Triple
T33443758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tocco Caudio |
E856434
|
entity |
| Predicate | hasAbandonmentCause |
P20519
|
FINISHED |
| Object | earthquakes |
—
|
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: earthquakes | Statement: [Tocco Caudio, hasAbandonmentCause, earthquakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAbandonmentCause Context triple: [Tocco Caudio, hasAbandonmentCause, earthquakes]
-
A.
abandonedReason
chosen
Indicates the reason or cause for which something was abandoned, discontinued, or given up.
-
B.
abandonedDuring
Indicates that one entity ceased support for or deserted another entity in the midst of an ongoing process, event, or period.
-
C.
abandonedBefore
Indicates that one entity ceased or gave up on something prior in time to another entity doing so.
-
D.
abandonmentType
Indicates the specific manner or category of how something or someone was abandoned in the described situation.
-
E.
abandonmentStart
Indicates the point in time or event at which an abandonment process or state begins between the involved entities.
- 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e4a5c8248190b4bf6942c586c69c |
completed | May 3, 2026, 6:01 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:37 a.m.