Triple
T37094387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Realms of Arnor and Gondor |
E918518
|
entity |
| Predicate | strategicRivers |
P188163
|
FINISHED |
| Object | Anduin |
—
|
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: Anduin | Statement: [Realms of Arnor and Gondor, strategicRivers, Anduin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategicRivers Context triple: [Realms of Arnor and Gondor, strategicRivers, Anduin]
-
A.
useRiverSystems
Indicates that an entity utilizes or manages river systems for a particular purpose or function.
-
B.
raceRiver
Indicates that an entity participates in a race that takes place on or along a river.
-
C.
majorRiverRole
Indicates that a river plays a primary or dominant role in a specified context, such as geography, economy, culture, or ecology, relative to other rivers in the area.
-
D.
associatedRiverBasin
Indicates that one entity is linked to, or lies within the drainage area of, a particular river basin.
-
E.
waterwaySystem
Indicates that one entity is part of, or belongs to, a connected network of waterways associated with another entity.
- F. None of above. chosen
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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fba28684208190921694f23e350c3b |
completed | May 6, 2026, 8:20 p.m. |
Created at: May 3, 2026, 4:14 p.m.