Triple
T33853376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sally |
E867695
|
entity |
| Predicate | entangledAfterEvent |
P91259
|
FINISHED |
| Object | mysterious car accident |
—
|
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: mysterious car accident | Statement: [Sally, entangledAfterEvent, mysterious car accident]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entangledAfterEvent Context triple: [Sally, entangledAfterEvent, mysterious car accident]
-
A.
entangledWith
Indicates a mutual state in which two or more entities are so interconnected that a change or condition in one inherently affects or constrains the other(s).
-
B.
closedAfterEvent
Indicates that an entity becomes or is marked as closed following the occurrence of a specified event.
-
C.
canBeEntangledIn
chosen
Indicates that one entity is capable of becoming physically or conceptually caught, intertwined, or ensnared within another entity or situation.
-
D.
laterRelatedEvent
Indicates that one event is temporally related to another by occurring at a later time.
-
E.
dissolvedAfterEvent
Indicates that an entity ceased to exist, function, or remain intact as a direct consequence of a specified event occurring beforehand.
- 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70075a0888190b3470cf7e5aaf482 |
completed | May 3, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.