Triple
T36546652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Unnumbered Tears |
E901157
|
entity |
| Predicate | locationPreviouslyKnownAs |
P45925
|
FINISHED |
| Object | Ard-galen |
E889543
|
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: Ard-galen | Statement: [Battle of Unnumbered Tears, locationPreviouslyKnownAs, Ard-galen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationPreviouslyKnownAs Context triple: [Battle of Unnumbered Tears, locationPreviouslyKnownAs, Ard-galen]
-
A.
cityPreviouslyLocatedIn
Indicates that a city was formerly situated within a specified location or administrative region, but is no longer located there.
-
B.
formerlyKnownLocationAs
Indicates that an entity was previously known or referred to by a different location name or designation.
-
C.
formerlyLocatedOn
Indicates that an entity was once located on or situated upon another entity, but is no longer in that position.
-
D.
locationSince
Indicates that an entity has been located at a particular place continuously since a specified point in time.
-
E.
previousLocationName
chosen
Indicates that one entity specifies the name of a location where another entity was situated or occurred before its current location.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a20b713188190aa8374ca834f55ba |
completed | June 23, 2026, 5:59 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.