Triple
T31384169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geva Theatre Center |
E800550
|
entity |
| Predicate | hasSecondStage |
P198758
|
FINISHED |
| Object | Fielding Stage |
—
|
NE NERFINISHED |
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: Fielding Stage | Statement: [Geva Theatre Center, hasSecondStage, Fielding Stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondStage Context triple: [Geva Theatre Center, hasSecondStage, Fielding Stage]
-
A.
secondStage
Indicates that something functions as the subsequent or follow-up stage in a multi-stage process or sequence.
-
B.
hasSecond
Indicates that one entity is the second item, position, or element in an ordered sequence or pair relative to another entity.
-
C.
secondStageType
Indicates the specific kind or category of a process, object, or event that occurs as the second stage in a multi-stage sequence.
-
D.
secondStageFrom
Indicates that one entity serves as the second stage derived from, or following after, another entity in a multi-stage process or structure.
-
E.
hasSecondLevel
Indicates that an entity possesses or is associated with a second hierarchical level within a structured system or classification.
- 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69ff0491409c8190be40f633a58da0b1 |
completed | May 9, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69ff040bb5cc81909534c7eee85d5e90 |
completed | May 9, 2026, 9:53 a.m. |
| PDg | Predicate description generation | batch_69ff04901ab081908b68563836fcdc99 |
completed | May 9, 2026, 9:55 a.m. |
Created at: April 29, 2026, 9:19 p.m.