Triple
T37553421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gromgol Base Camp |
E933640
|
entity |
| Predicate | hasZeppelinRouteTo |
P187042
|
FINISHED |
| Object | Orgrimmar |
—
|
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: Orgrimmar | Statement: [Gromgol Base Camp, hasZeppelinRouteTo, Orgrimmar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasZeppelinRouteTo Context triple: [Gromgol Base Camp, hasZeppelinRouteTo, Orgrimmar]
-
A.
hasRoute
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
B.
hasRouteDestination
chosen
Indicates that a route leads to or terminates at a specified destination.
-
C.
includesRouteBetween
Indicates that one entity (such as a service, plan, or network) contains or provides a specific route connecting two locations or points.
-
D.
hasRouteFeature
Indicates that a route possesses or is associated with a specific characteristic, attribute, or feature.
-
E.
hasRouteConsideration
Indicates that one entity takes another entity into account when planning, evaluating, or determining a route.
- 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_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.