Triple
T38585377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frostfire Ridge |
E932333
|
entity |
| Predicate | containsGarrisonType |
P143638
|
FINISHED |
| Object | Horde Garrison |
—
|
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: Horde Garrison | Statement: [Frostfire Ridge, containsGarrisonType, Horde Garrison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsGarrisonType Context triple: [Frostfire Ridge, containsGarrisonType, Horde Garrison]
-
A.
garrisonType
Indicates the specific kind or classification of military garrison associated with an entity.
-
B.
garrisonForceType
Indicates the specific type or classification of military force assigned to occupy, defend, or maintain control of a particular location.
-
C.
garrisonOrCrewType
chosen
Indicates the specific kind of garrison or crew assigned to occupy, staff, or operate a given entity.
-
D.
garrisonIncluded
Indicates that a particular garrison is included within, or forms part of, a specified larger military force, unit, or installation.
-
E.
hasGarrisonOutpostChoice
Indicates that an entity is associated with a selectable option regarding the placement or use of a garrison outpost.
- 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_6a0248062e608190aae1afdae38d2e5a |
completed | May 11, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_6a02465a0d38819084c3a6813fb943fc |
completed | May 11, 2026, 9:12 p.m. |
Created at: May 3, 2026, 4:32 p.m.