Triple
T17265623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marla Singer |
E419118
|
entity |
| Predicate | fakesCondition |
P126785
|
FINISHED |
| Object | various terminal illnesses |
—
|
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: various terminal illnesses | Statement: [Marla Singer, fakesCondition, various terminal illnesses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fakesCondition Context triple: [Marla Singer, fakesCondition, various terminal illnesses]
-
A.
falseFor
Indicates that a given statement or proposition does not hold true or is invalid specifically in the context of the referenced entity or situation.
-
B.
supportsCondition
Indicates that one entity helps maintain, enable, or is compatible with a particular condition or state in another entity.
-
C.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
D.
holdsUnderCondition
Indicates that one fact, rule, or relationship remains valid only when a specified condition or set of conditions is satisfied.
-
E.
cloneCondition
Indicates that one entity is a duplicate or replication of another under the same specified conditions or parameters.
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f44ec7c81909a925fc8692b0a6c |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
| PDg | Predicate description generation | batch_69e39c2fedb881908bfed2c3e5f2616a |
completed | April 18, 2026, 2:58 p.m. |
Created at: April 10, 2026, 5:40 a.m.