Triple
T38589145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lower Spire |
E932412
|
entity |
| Predicate | vehicleEncounter |
P178671
|
FINISHED |
| Object | Icecrown Gunship Battle |
—
|
NE NERFINISHED |
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: Icecrown Gunship Battle | Statement: [The Lower Spire, vehicleEncounter, Icecrown Gunship Battle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleEncounter Context triple: [The Lower Spire, vehicleEncounter, Icecrown Gunship Battle]
-
A.
vehicleInScene
chosen
Indicates that a vehicle is present or appears within a particular scene.
-
B.
visitingVehicle
Indicates a relationship where a vehicle temporarily arrives at or is present at a location that is not its usual or home base.
-
C.
vehicleObsession
Indicates an intense, often excessive preoccupation or fixation that one entity has with vehicles.
-
D.
utilityInvolved
Indicates that a utility service or provider is involved in, associated with, or plays a role in the referenced situation or relationship.
-
E.
vehicleCarrying
Indicates that one vehicle is transporting, holding, or supporting another entity as its load or cargo.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 3, 2026, 4:32 p.m.