Triple
T37036355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argonath |
E916647
|
entity |
| Predicate | locatedBetweenRegions |
P1262
|
FINISHED |
| Object | Nen Hithoel and the Emyn Muil |
E2189447
|
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: Nen Hithoel and the Emyn Muil | Statement: [Argonath, locatedBetweenRegions, Nen Hithoel and the Emyn Muil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedBetweenRegions Context triple: [Argonath, locatedBetweenRegions, Nen Hithoel and the Emyn Muil]
-
A.
locatedBetween
chosen
Indicates that one entity is positioned spatially between two other reference entities.
-
B.
operatesBetweenRegion
Indicates a relationship in which an entity conducts operations or provides services that connect or span between two distinct regions.
-
C.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
D.
regionIs
Indicates that one entity is located within, belongs to, or is associated with a specified geographic or administrative region.
-
E.
locatedNearRegion
Indicates that one entity is situated in close geographic proximity to a specified region.
- 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e8c3ce7448190a166c2dd0d00a1a3 |
completed | June 26, 2026, 2:27 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.