Triple
T38643686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warfronts |
E938664
|
entity |
| Predicate | firstWarfrontLocation |
P8094
|
FINISHED |
| Object | Arathi Highlands |
E2158035
|
NE 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: Arathi Highlands | Statement: [Warfronts, firstWarfrontLocation, Arathi Highlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstWarfrontLocation Context triple: [Warfronts, firstWarfrontLocation, Arathi Highlands]
-
A.
otherWarfrontLocation
Indicates that an entity is located at a different warfront or battle location than another referenced warfront location.
-
B.
firstLocation
chosen
Indicates the initial or primary place where an entity is situated, originates, or where an event or relationship begins.
-
C.
fortressLocation
Indicates that a fortress is located at or in a specified place or geographic area.
-
D.
wartimeLocation
Indicates the location where an entity is situated or operates during a period of war or armed conflict.
-
E.
firstCombatUseLocation
Indicates the location where something (typically a weapon, system, or tactic) was used in combat for the first time.
- F. None of above.
Provenance (4 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41fd5af02881909ad15dad80929473 |
completed | June 29, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.