Triple
T37551717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borean Tundra |
E933604
|
entity |
| Predicate | majorFactionPresence |
P17876
|
FINISHED |
| Object | 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: Horde | Statement: [Borean Tundra, majorFactionPresence, Horde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorFactionPresence Context triple: [Borean Tundra, majorFactionPresence, Horde]
-
A.
hasMajorFaction
chosen
Indicates that an entity possesses or is associated with a primary or dominant faction within a given context.
-
B.
alliedForcePresence
Indicates the presence of military or security forces that are formally allied or cooperating with a given actor in a specific area or context.
-
C.
commandingForceSize
Indicates the size or magnitude of the military or organizational force that is exercising command or control in a given context.
-
D.
factionCount
Indicates the number of distinct factions associated with or involved in a given context or entity.
-
E.
hasApproximateDefendingForceSize
Indicates that an entity is associated with a defending force whose size is known only approximately rather than as an exact value.
- 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_6a000efe971081909de03f875a7ad6cc |
completed | May 10, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_6a000c4ffe788190a5757af60aadd9f3 |
completed | May 10, 2026, 4:40 a.m. |
Created at: May 3, 2026, 4:17 p.m.