Triple
T6829138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myus |
E157091
|
entity |
| Predicate | abandonedDueTo |
P20519
|
FINISHED |
| Object | silting of the Maeander River |
—
|
LITERAL 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: silting of the Maeander River | Statement: [Myus, abandonedDueTo, silting of the Maeander River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abandonedDueTo Context triple: [Myus, abandonedDueTo, silting of the Maeander River]
-
A.
abandonedReason
chosen
Indicates the reason or cause for which something was abandoned, discontinued, or given up.
-
B.
abandonedBy
Indicates that one entity has been deserted, forsaken, or left behind by another entity that was previously present, responsible, or involved.
-
C.
abandonedIn
Indicates that one entity was left behind or deserted in the location or context specified by another entity.
-
D.
abandonmentType
Indicates the specific manner or category of how something or someone was abandoned in the described situation.
-
E.
abandonedAfterEvent
Indicates that one entity ceased support for, left, or discontinued involvement with another entity following a specific event or occurrence.
- 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_69c6882a5b5c8190917a7db9ed36bad1 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d626df448190b4b1d7406d571d07 |
completed | March 27, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69c6d09d95f0819091ca7f897dc21efe |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.