Triple
T36417122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darren Fletcher |
E897039
|
entity |
| Predicate | tookBreakFrom |
P96419
|
FINISHED |
| Object | professional football due to illness |
—
|
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: professional football due to illness | Statement: [Darren Fletcher, tookBreakFrom, professional football due to illness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookBreakFrom Context triple: [Darren Fletcher, tookBreakFrom, professional football due to illness]
-
A.
tookBreakFromFootball
chosen
Indicates that an entity temporarily stopped participating in football for a period of time.
-
B.
tookHiatusFromModeling
Indicates that an individual temporarily paused or interrupted their modeling career or activities.
-
C.
breakType
Indicates the specific kind or category of break or interruption that occurs in a process, activity, or sequence.
-
D.
break
Indicates that one entity causes another entity to separate into pieces, stop functioning, or otherwise lose its normal integrity or continuity.
-
E.
formedByBreakWith
Indicates that something came into existence as a result of a split, rupture, or separation from a prior entity or group.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.