Triple
T38585450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanaan Jungle |
E932335
|
entity |
| Predicate | factionStrongholdOf |
P46785
|
FINISHED |
| Object | Iron Horde |
—
|
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: Iron Horde | Statement: [Tanaan Jungle, factionStrongholdOf, Iron Horde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: factionStrongholdOf Context triple: [Tanaan Jungle, factionStrongholdOf, Iron Horde]
-
A.
strongholdOf
chosen
Indicates that a location serves as a primary fortified base, center of power, or main stronghold for a particular entity.
-
B.
primaryStronghold
Indicates that one location serves as the main base, fortress, or central stronghold for an entity compared to its other sites.
-
C.
traditionalPartyStronghold
Indicates that a particular area or region has historically and consistently provided strong electoral support for a traditional or long-established political party.
-
D.
fortifiedSite
Indicates a site that has been strengthened or defended with protective structures or measures against attack.
-
E.
strongholdRegion
Indicates that a stronghold (fortified place or base) is located within or associated with a particular geographic region.
- 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_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 3, 2026, 4:32 p.m.