Triple
T23816517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calico Mine Ride |
E589109
|
entity |
| Predicate | showScenesInclude |
P47737
|
FINISHED |
| Object | loading station in mine yard |
—
|
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: loading station in mine yard | Statement: [Calico Mine Ride, showScenesInclude, loading station in mine yard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showScenesInclude Context triple: [Calico Mine Ride, showScenesInclude, loading station in mine yard]
-
A.
includesShow
Indicates that one entity contains or features a particular show as part of its content or offerings.
-
B.
containsScene
chosen
Indicates that one entity (typically a media item or narrative work) includes or features a particular scene as part of its content.
-
C.
numberOfScenes
Indicates the total count of distinct scenes associated with or contained within an entity.
-
D.
scenes
Indicates that one entity is a scene or setting in which the other entity occurs, appears, or is depicted.
-
E.
featuresSceneFrom
Indicates that one entity (such as a work or media item) includes or presents a particular scene taken from another entity.
- 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7ab4e8881908f2711e9d62cad98 |
completed | April 29, 2026, 8:56 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:58 p.m.