Triple
T24818389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maeander River basin |
E620986
|
entity |
| Predicate | toponymForm |
P9174
|
FINISHED |
| Object | Μαίανδρος (Maiandros) |
—
|
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: Μαίανδρος (Maiandros) | Statement: [Maeander River basin, toponymForm, Μαίανδρος (Maiandros)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toponymForm Context triple: [Maeander River basin, toponymForm, Μαίανδρος (Maiandros)]
-
A.
hasToponymicForm
chosen
Indicates that one entity is a toponymic (place-name-based) form or variant derived from another entity.
-
B.
toponymsShareSpelling
Indicates that two place names share the same or very similar written form or spelling.
-
C.
toponymicFunction
Indicates that one entity functions as a place-related name or designation for another entity, typically identifying or characterizing it by a geographic location.
-
D.
includesToponym
Indicates that one entity contains or references a place name (toponym) associated with another entity.
-
E.
toponymRefersTo
Indicates that a place name (toponym) designates or refers to a specific geographic entity or location.
- F. None of above.
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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:04 a.m.