Triple
T22910167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eisenhower Tree |
E568566
|
entity |
| Predicate | removedAfter |
P150195
|
FINISHED |
| Object | ice storm damage |
—
|
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: ice storm damage | Statement: [Eisenhower Tree, removedAfter, ice storm damage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: removedAfter Context triple: [Eisenhower Tree, removedAfter, ice storm damage]
-
A.
removedBefore
Indicates that one entity was removed or taken away earlier in time than another specified entity or event.
-
B.
removedOn
Indicates that an entity was taken away, deleted, or detached at a specific point in time.
-
C.
removedFrom
Indicates that one entity has been taken away, extracted, or detached from another entity or context.
-
D.
laterRemovedTo
Indicates that an entity was moved or transferred to a location or state at a later time, after an earlier condition or placement.
-
E.
afterRemoval
Indicates that a condition, state, or relationship holds only once a specified entity or element has been removed.
- F. None of above. chosen
Provenance (4 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_69e2458cd9e48190943ad2e34485d939 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1807350008190a057e8fb5c363c5f |
completed | April 29, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:42 p.m.