Triple
T36035570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tralee Ship Canal |
E1042386
|
entity |
| Predicate | causeOfDisuse |
P163169
|
FINISHED |
| Object | decline in commercial traffic |
—
|
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: decline in commercial traffic | Statement: [Tralee Ship Canal, causeOfDisuse, decline in commercial traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfDisuse Context triple: [Tralee Ship Canal, causeOfDisuse, decline in commercial traffic]
-
A.
obsoleteReason
chosen
Indicates the reason or justification for why something has become obsolete or is no longer in use.
-
B.
fellIntoNeglect
Indicates that something previously maintained or attended to was no longer cared for and gradually deteriorated or was forgotten.
-
C.
ceasedToBeUsed
Indicates that something that was previously in use has stopped being used from a certain point in time onward.
-
D.
decayResistanceCause
Indicates that one factor or condition is the cause of another entity’s resistance to decay.
-
E.
decay
Indicates a process by which something gradually breaks down, deteriorates, or loses its original structure or quality over time.
- 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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: May 3, 2026, 4:07 p.m.