Triple
T13083644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eli Cash |
E310272
|
entity |
| Predicate | hasCarAccident |
P32122
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Eli Cash, hasCarAccident, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCarAccident Context triple: [Eli Cash, hasCarAccident, yes]
-
A.
hasAccidentAt
Indicates that an accident involving a subject occurs at a specific location or time.
-
B.
hasModeOfTransportInAccident
Indicates that a specific mode of transport was involved in an accident associated with the given entity.
-
C.
involvedInAccident
chosen
Indicates that an entity participated in, was affected by, or was otherwise a party to a specific accident or collision event.
-
D.
causedAccident
Indicates that one entity is responsible for bringing about or initiating an accident involving another entity or situation.
-
E.
hasInjuredPerson
Indicates that an entity has a person who has been harmed or injured associated with it.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9811add9881908a92186dab5b6d48 |
completed | April 10, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:02 p.m.