Triple
T36103605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf of Latmus |
E1044289
|
entity |
| Predicate | siltedBy |
P127677
|
FINISHED |
| Object | Maeander River |
—
|
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: Maeander River | Statement: [Gulf of Latmus, siltedBy, Maeander River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siltedBy Context triple: [Gulf of Latmus, siltedBy, Maeander River]
-
A.
jiltedBy
Indicates that one entity was suddenly rejected or abandoned in a romantic or emotional relationship by another entity.
-
B.
sillage
Indicates the lingering trail or trace left behind by something (such as a scent, movement, or presence) as it moves through space.
-
C.
hasSedimentsThat
Indicates that one entity contains, includes, or is associated with specific sediments described by the related entity.
-
D.
historicalWaterwaySiltedUpBy
chosen
Indicates that a formerly navigable or flowing waterway has become filled or obstructed by silt due to the action or influence of the related entity.
-
E.
submergedBy
Indicates that one entity is covered or overwhelmed by liquid, typically water, to the point of being beneath its surface due to the action or presence of another entity.
- 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_69f76e338e2c8190b7f3bc68bec76349 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.