Triple
T2497966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dibang River |
E52395
|
entity |
| Predicate | passesNear |
P416
|
FINISHED |
| Object | Roing |
E209862
|
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: Roing | Statement: [Dibang River, passesNear, Roing]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Roing Context triple: [Dibang River, passesNear, Roing]
-
A.
Roing
chosen
Roing is a prominent town in northeastern India known as an important administrative and commercial center in the Lower Dibang Valley district of Arunachal Pradesh.
-
B.
Trou-ringh
Trou-ringh is a didactic emblem book by Dutch poet and moralist Jacob Cats that offers moral lessons through allegorical illustrations and verse.
-
C.
Ringen
Ringen is a station on the Oslo Metro system that serves as a key endpoint for certain metro lines in Norway’s capital.
-
D.
ROKN
ROKN is the abbreviation for the Republic of Korea Navy, the maritime branch of South Korea’s armed forces.
-
E.
Rycken
Rycken is a Dutch-origin surname historically borne by families such as that of Abraham Rycken in the Low Countries and early colonial America.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ab4957b3a88190adf968ae0c1b931c |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd1ad2f8c81908853e97d75081e84 |
completed | March 7, 2026, 7:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af1f9be594819099a03a2784691124 |
completed | March 9, 2026, 7:29 p.m. |
Created at: March 6, 2026, 9:46 p.m.