Triple
T25856238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wrong Mountain |
E651351
|
entity |
| Predicate | hasOriginalProductionType |
P140396
|
FINISHED |
| Object | stage production |
—
|
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: stage production | Statement: [Wrong Mountain, hasOriginalProductionType, stage production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalProductionType Context triple: [Wrong Mountain, hasOriginalProductionType, stage production]
-
A.
hasOriginalProgrammingType
Indicates that an entity has a specific type or category of original programming associated with it.
-
B.
hasOriginalComposition
Indicates that one entity is the initial or primary compositional source or makeup of another entity.
-
C.
hasOriginalVersion
Indicates that one entity is the original or initial version from which another entity is derived or adapted.
-
D.
originallyProducedAs
chosen
Indicates that one entity was first created, released, or manufactured in the form of another specified entity or format.
-
E.
hasOriginalWorkSetting
Indicates that an entity is associated with the setting or context in which the original work or source material takes place.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 22, 2026, 8 a.m.