Triple
T19797496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colin Craven |
E475580
|
entity |
| Predicate | laterPhysicalCondition |
P13710
|
FINISHED |
| Object | healthy |
—
|
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: healthy | Statement: [Colin Craven, laterPhysicalCondition, healthy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPhysicalCondition Context triple: [Colin Craven, laterPhysicalCondition, healthy]
-
A.
currentPhysicalStatus
Indicates the present condition or state of an entity’s physical being or body.
-
B.
physicallyConditionedAs
Indicates that one entity has been brought into or exists in a particular physical state or condition as specified by another entity or descriptor.
-
C.
laterStatus
chosen
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
D.
sufferedCondition
Indicates that an entity experienced or was afflicted by a particular condition, typically adverse or harmful, at some point in time.
-
E.
injuryStatus
Indicates the condition or state of harm, damage, or physical injury affecting an entity.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e653c877288190b56ee7eedea710a3 |
completed | April 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.