Triple
T36822415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Carnen |
E909920
|
entity |
| Predicate | nearByRegion |
P55639
|
FINISHED |
| Object | lands of the Easterlings |
—
|
LITERAL 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: lands of the Easterlings | Statement: [River Carnen, nearByRegion, lands of the Easterlings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearByRegion Context triple: [River Carnen, nearByRegion, lands of the Easterlings]
-
A.
nearbySettlementRegion
Indicates that a settlement is located close to or within the surrounding area of a specified region.
-
B.
nearbyRegionCharacterizedBy
Indicates that a region located nearby another entity is defined or distinguished by a particular characteristic, feature, or condition.
-
C.
featuresRegionalProximity
chosen
Indicates that one entity is located near or in close geographic proximity to a particular region or another entity.
-
D.
nearbyRegionAcrossSea
Indicates that one region is geographically close to another, with a sea lying between them.
-
E.
nearProvince
Indicates that one province is geographically close to or bordering another province.
- 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_69f76e7dd13c81908c60b05adb49eeb5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fefa064ab48190925759950d0d94d9 |
completed | May 9, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69fef96ae5d08190b027435753c44821 |
completed | May 9, 2026, 9:07 a.m. |
Created at: May 3, 2026, 4:13 p.m.