Triple
T3957853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corinth Canal |
E85823
|
entity |
| Predicate | maintenanceIssue |
P13650
|
FINISHED |
| Object | landslides |
—
|
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: landslides | Statement: [Corinth Canal, maintenanceIssue, landslides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintenanceIssue Context triple: [Corinth Canal, maintenanceIssue, landslides]
-
A.
maintenanceFeature
Indicates that one entity serves as a maintenance-related feature, capability, or component associated with another entity.
-
B.
maintenance
Indicates that an entity performs, requires, or is involved in upkeep, repair, or preservation activities for another entity or system.
-
C.
facingIssue
chosen
Indicates that an entity is currently experiencing, encountering, or dealing with a problem, difficulty, or obstacle.
-
D.
laterOperationalIssue
Indicates that an operational issue occurred at some point after a referenced time, event, or condition.
-
E.
platformIssue
Indicates that there is a problem, malfunction, or limitation affecting the operation or availability of a platform.
- 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_69aed93a96908190bcbdbfa718f155bd |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaa5afdc8190b709af2473d75d02 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8ed04e4819096bced8971cd888d |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:31 p.m.