Triple
T10557908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robin Cavendish |
E249135
|
entity |
| Predicate | livedWithConditionFor |
P94666
|
FINISHED |
| Object | over 35 years |
—
|
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: over 35 years | Statement: [Robin Cavendish, livedWithConditionFor, over 35 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livedWithConditionFor Context triple: [Robin Cavendish, livedWithConditionFor, over 35 years]
-
A.
livedWith
Indicates that two entities shared the same residence or household for a period of time.
-
B.
livedBefore
Indicates that one entity existed or was alive at an earlier time than another entity.
-
C.
livedDuring
Indicates that the subject existed or was alive at some point within the time period or lifespan associated with the object.
-
D.
associatedWithCondition
Indicates that an entity has a relevant connection or linkage to a particular condition (such as a disease, state, or circumstance), without specifying the nature or strength of that connection.
-
E.
holdsUnderCondition
Indicates that one fact, rule, or relationship remains valid only when a specified condition or set of conditions is satisfied.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5271521a4819086d96e1f183ab07a |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d518fa0b4081909bffc936d78bd77b |
completed | April 7, 2026, 2:47 p.m. |
| PDg | Predicate description generation | batch_69d5270eca0481908573b698390c5b08 |
completed | April 7, 2026, 3:47 p.m. |
Created at: April 6, 2026, 12:35 p.m.