Triple
T19941593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chorus of Theban Elders |
E479318
|
entity |
| Predicate | functionInStructure |
P137938
|
FINISHED |
| Object | unifies episodic scenes |
—
|
LITERAL 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: unifies episodic scenes | Statement: [Chorus of Theban Elders, functionInStructure, unifies episodic scenes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInStructure Context triple: [Chorus of Theban Elders, functionInStructure, unifies episodic scenes]
-
A.
functionInSystem
Indicates that an entity serves a specific role or performs a particular function within a given system.
-
B.
functionInText
Indicates that a text segment serves a specific rhetorical or structural function within a larger text.
-
C.
functionInBuilding
Indicates that a specific function, role, or use is carried out within a particular building.
-
D.
functionInWork
Indicates that a particular function, role, or operation is performed, utilized, or occurs within the context of a specific work or creation.
-
E.
functionInName
Indicates that the name of one entity includes or references the function or role of another entity.
- F. None of above. chosen
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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a6318848190a1dd3e0a6fea3fe2 |
completed | April 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:54 p.m.