Triple
T12932655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celaenae |
E309421
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Maeander River |
E1012016
|
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: Maeander River | Statement: [Celaenae, locatedOn, Maeander River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maeander River Context triple: [Celaenae, locatedOn, Maeander River]
-
A.
Maeander River
chosen
The Maeander River is an ancient river in western Anatolia, famed for its extremely winding course that gave rise to the word “meander.”
-
B.
Gediz River
The Gediz River is a major river in western Turkey that flows into the Aegean Sea near the city of Izmir.
-
C.
Halys River
The Halys River is the ancient name for the Kızılırmak River, the longest river entirely within modern-day Turkey and a historically significant boundary in Anatolia.
-
D.
Tarsus River
The Tarsus River is a waterway in southern Turkey that flows through the historic city of Tarsus before reaching the Mediterranean Sea.
-
E.
Aderde
Aderde is a town located in the Anseba region of Eritrea.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97dc6517481908637781da240b51f |
completed | April 10, 2026, 10:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6c0eaa3688190b399aa212e16ca08 |
completed | May 3, 2026, 3:28 a.m. |
Created at: April 9, 2026, 5:42 p.m.