Triple
T3519834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Teller |
E74393
|
entity |
| Predicate | deathConsidered |
P48501
|
FINISHED |
| Object | suspicious |
—
|
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: suspicious | Statement: [John Teller, deathConsidered, suspicious]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathConsidered Context triple: [John Teller, deathConsidered, suspicious]
-
A.
deathStatus
Indicates whether an entity is alive, dead, or in another specified state related to mortality.
-
B.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
-
C.
death
Indicates the event or state in which an entity ceases to live or exist, marking the end of its biological or functional processes.
-
D.
deathContributedTo
Indicates that one entity played a causal or contributing role in bringing about the death of another entity.
-
E.
deathBefore
Indicates that one entity’s death occurred earlier in time than another entity’s death.
- 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc4af70c8190a7471f28e1efd7fd |
completed | March 8, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69adae10689c8190b7dc6d7daa8295b6 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaed74ecc8190b74dc70ab59a3e1c |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:19 p.m.