Triple
T37553663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Searing Gorge |
E933644
|
entity |
| Predicate | hasTravelConnection |
P105188
|
FINISHED |
| Object | flight path to Ironforge (Alliance) |
—
|
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: flight path to Ironforge (Alliance) | Statement: [Searing Gorge, hasTravelConnection, flight path to Ironforge (Alliance)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTravelConnection Context triple: [Searing Gorge, hasTravelConnection, flight path to Ironforge (Alliance)]
-
A.
hasAirTravelLink
chosen
Indicates that there is a direct or established air travel connection (such as flights or air routes) between the related entities.
-
B.
hasTravelNetwork
Indicates that one entity possesses, manages, or is connected through a system or infrastructure enabling travel or transportation between locations.
-
C.
hasTravelType
Indicates the mode or category of travel associated with a given trip, journey, or movement event.
-
D.
connectsTravelBetween
Indicates a relationship where something (such as a route, service, or mode of transport) enables or provides travel between two locations.
-
E.
traveledToBy
Indicates that an entity has been traveled to or visited by 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a003ffb548081908ba64fd2b570f42f |
completed | May 10, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_6a003fcecf788190a13dff38b9de3414 |
completed | May 10, 2026, 8:20 a.m. |
Created at: May 3, 2026, 4:17 p.m.