Triple
T37539324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talador |
E933284
|
entity |
| Predicate | hasGarrisonOutpost |
P36256
|
FINISHED |
| Object | Alliance Garrison Outpost |
—
|
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: Alliance Garrison Outpost | Statement: [Talador, hasGarrisonOutpost, Alliance Garrison Outpost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGarrisonOutpost Context triple: [Talador, hasGarrisonOutpost, Alliance Garrison Outpost]
-
A.
hasFortressConstructed
Indicates that a fortress has been built or established for, by, or at the associated entity.
-
B.
isRemoteOutpostFor
Indicates that one location functions as a distant, often isolated operational base or support site for another primary location or organization.
-
C.
garrisonOrHQ
chosen
Indicates that an entity serves as a military garrison or headquarters location for another entity.
-
D.
garrisonOrMobilizationPoint
Indicates a location where military forces are stationed, assembled, or prepared for deployment or mobilization.
-
E.
garrisonIncluded
Indicates that a particular garrison is included within, or forms part of, a specified larger military force, unit, or installation.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.