Triple
T37331486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stage Manager (Our Town) |
E926762
|
entity |
| Predicate | controlsOnstageTime |
P199356
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Stage Manager (Our Town), controlsOnstageTime, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlsOnstageTime Context triple: [Stage Manager (Our Town), controlsOnstageTime, true]
-
A.
timeToControl
Indicates the amount of time required for an entity to gain or establish control over another entity, process, or situation.
-
B.
coreStageLength
Indicates the length or duration of the main or primary stage within a multi-stage process or structure.
-
C.
screenTimePhase
Indicates the specific stage or period within a broader screen-time process, session, or lifecycle that an entity is currently in.
-
D.
openingSceneTime
Indicates the specific time at which the opening scene of a work (e.g., film, play, or episode) takes place within its narrative.
-
E.
timeOfKeyScene
Indicates the specific time at which a key or pivotal scene occurs within a larger sequence or event.
- 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff2fbae9b48190847eefa1c227d43e |
completed | May 9, 2026, 12:59 p.m. |
| PD | Predicate disambiguation | batch_69ff2f2218048190a32224a648182b5d |
completed | May 9, 2026, 12:57 p.m. |
| PDg | Predicate description generation | batch_69ff2fb9e46c8190b36b3e0bc84f114c |
completed | May 9, 2026, 12:59 p.m. |
Created at: May 3, 2026, 4:16 p.m.