Triple
T3170338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Somewhere |
E66314
|
entity |
| Predicate | usedInScene |
P25490
|
FINISHED |
| Object | dream ballet sequence (stage version, often) |
—
|
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: dream ballet sequence (stage version, often) | Statement: [Somewhere, usedInScene, dream ballet sequence (stage version, often)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInScene Context triple: [Somewhere, usedInScene, dream ballet sequence (stage version, often)]
-
A.
areUsedIn
chosen
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
B.
usedInState
Indicates that something is employed, applied, or functions within a particular state or condition.
-
C.
hasInfluenceFromScene
Indicates that something is affected, shaped, or guided by the characteristics or context of a particular scene.
-
D.
usedInTheatre
Indicates that something is employed or applied within the context of a theatre or theatrical production.
-
E.
usedInStructure
Indicates that something (such as a material, component, or element) is employed as part of the composition or construction of a larger structure.
- 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_69ad8585d7988190af37365331093ccd |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada64917e08190bf0466d2c5e43790 |
completed | March 8, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0076b4819094628f1ad10b8f68 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.