Triple
T37369068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calenardhon foothills |
E927787
|
entity |
| Predicate | laterNameOfRegionContext |
P171724
|
FINISHED |
| Object | Rohan |
—
|
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: Rohan | Statement: [Calenardhon foothills, laterNameOfRegionContext, Rohan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterNameOfRegionContext Context triple: [Calenardhon foothills, laterNameOfRegionContext, Rohan]
-
A.
regionNamedAfter
Indicates that a geographic region derives its name from a specific person, place, event, or other entity.
-
B.
laterNamedBy
Indicates that an entity received its name from another entity at a later point in time.
-
C.
formerNameOfRegion
chosen
Indicates that one name was previously used for a region that is now known by a different name.
-
D.
laterNamed
Indicates that an entity was given a new name at a later time, linking its original identity to its subsequent name.
-
E.
laterAdministrativeRegion
Indicates that an entity became part of, or was replaced by, another administrative region at a later point in time.
- 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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0117b6539c8190be7d231e891fe546 |
completed | May 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_6a011762f7ec8190afc884b92419d33f |
completed | May 10, 2026, 11:40 p.m. |
Created at: May 3, 2026, 4:16 p.m.