Triple
T38115158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Science Fiction/Double Feature |
E951767
|
entity |
| Predicate | positionInStageShow |
P15235
|
FINISHED |
| Object | opening number |
—
|
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: opening number | Statement: [Science Fiction/Double Feature, positionInStageShow, opening number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInStageShow Context triple: [Science Fiction/Double Feature, positionInStageShow, opening number]
-
A.
positionInShow
chosen
Indicates the specific order or placement an entity occupies within a show, series, or sequence of performances or episodes.
-
B.
positionInAct
Indicates the specific location or role that something occupies within a particular act or segment of a larger sequence or performance.
-
C.
positionOnTheatre
Indicates the spatial location or placement of something within the layout or seating/area arrangement of a theatre.
-
D.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
E.
appearsAtPosition
Indicates that an entity occurs or is located at a specific position within an ordered structure or sequence.
- F. None of above.
Provenance (3 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_69f76f07734c8190814e937e12257a78 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00119d821c8190874786391b27ef23 |
completed | May 10, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_6a001143fb6881909ac0ae8bfea04351 |
completed | May 10, 2026, 5:01 a.m. |
Created at: May 3, 2026, 4:21 p.m.