Triple
T35710497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Théâtre Libre |
E1031841
|
entity |
| Predicate | notablePlaywrightStaged |
P60080
|
FINISHED |
| Object | Henrik Ibsen |
E116631
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Henrik Ibsen | Statement: [Théâtre Libre, notablePlaywrightStaged, Henrik Ibsen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlaywrightStaged Context triple: [Théâtre Libre, notablePlaywrightStaged, Henrik Ibsen]
-
A.
notablePlaywrightProduced
Indicates that a notable playwright created or authored the referenced play or dramatic work.
-
B.
notablePlaywrightsPerformed
chosen
Indicates that the subject has performed works written by the object, who is a notable playwright.
-
C.
notablePlaywrightAssociated
Indicates a relationship where a notable playwright is significantly connected or linked to an entity, such as through authorship, collaboration, or influential association.
-
D.
notableActorInStageProduction
Indicates that a person is a distinguished or prominent actor in a particular stage production.
-
E.
notableTheaterWork
Indicates that a theater work is notably associated with, or a significant part of the achievements of, a given entity.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76e0df1d08190965b1c6dff94c391 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a387d10645481908dd97e6254aa9f63 |
completed | June 22, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.