Triple
T27049363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polygraph |
E684721
|
entity |
| Predicate | hasPlaywrightDirector |
P175218
|
FINISHED |
| Object | Robert Lepage |
E175117
|
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: Robert Lepage | Statement: [Polygraph, hasPlaywrightDirector, Robert Lepage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlaywrightDirector Context triple: [Polygraph, hasPlaywrightDirector, Robert Lepage]
-
A.
hasPlaywrightDebutFor
Indicates that an entity made their first appearance or debut as a playwright specifically for a given work, production, or context.
-
B.
hasArtDirector
Indicates that an entity has a specific person or organization serving as its art director.
-
C.
hasDirectorScreenwriter
Indicates that a director is also the screenwriter (or one of the screenwriters) for a given work.
-
D.
hasDirectorOfWork
Indicates that an entity has a specific person or organization serving as the director responsible for overseeing its work or project.
-
E.
hasDirectorInKeyWork
Indicates that a director is associated with a key or primary work of an entity (such as a film, series, or major production).
- F. None of above. chosen
Provenance (5 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a15d7719698819096c1a27507cd1b92 |
completed | May 26, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cee3604c81908a07eade2f39064e |
completed | May 3, 2026, 4:28 a.m. |
Created at: April 27, 2026, 8:13 a.m.