Triple
T14638000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volantis |
E343654
|
entity |
| Predicate | locatedAtMouthOf |
P165
|
FINISHED |
| Object | Rhoyne |
E731098
|
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: Rhoyne | Statement: [Volantis, locatedAtMouthOf, Rhoyne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rhoyne Context triple: [Volantis, locatedAtMouthOf, Rhoyne]
-
A.
Lez River
The Lez River is a short coastal river in southern France that flows through the city of Montpellier before emptying into the Mediterranean Sea.
-
B.
River Hodder
River Hodder is a river in Lancashire, England, known for flowing through the Forest of Bowland and joining the River Ribble near Great Mitton.
-
C.
Orbieu River
The Orbieu River is a watercourse in southern France that flows through the Aude department and joins the Aude River.
-
D.
River Whye
chosen
River Whye is a fictional river in Stephen King’s Dark Tower universe, flowing through the central realm known as Mid-World.
-
E.
River Dour
The River Dour is a small chalk stream in Kent, England, that flows through the Dover area and historically powered local mills.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4aca6448190adf1042dfbfef716 |
completed | April 14, 2026, 9:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fec86ea50c819083d0bbed4c459041 |
completed | May 9, 2026, 5:38 a.m. |
Created at: April 10, 2026, 1:26 a.m.