Triple
T28891967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phiona Mutesi |
E732721
|
entity |
| Predicate | hasNotableLifeEvent |
P53982
|
FINISHED |
| Object | transition from street vending to competitive chess |
—
|
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: transition from street vending to competitive chess | Statement: [Phiona Mutesi, hasNotableLifeEvent, transition from street vending to competitive chess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableLifeEvent Context triple: [Phiona Mutesi, hasNotableLifeEvent, transition from street vending to competitive chess]
-
A.
notableEventInLife
chosen
Indicates that a particular event holds significant importance or impact within an entity’s life or personal history.
-
B.
hasNotablePersonEvent
Indicates that there exists a significant event in which the person plays a notable or central role.
-
C.
hasPartInLife
Indicates that an entity participates in, contributes to, or plays a role within some aspect or period of another entity’s life.
-
D.
hasNotableYear
Indicates that an entity is associated with a specific year that is particularly significant or noteworthy for it.
-
E.
hasNotableEventName
Indicates that an entity is associated with a notable event identified by a specific name.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69ff5f5ecc808190b2df364da108ff4c |
completed | May 9, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ff5b84131c8190bf81d7fb53e934bc |
completed | May 9, 2026, 4:06 p.m. |
Created at: April 28, 2026, 7:56 a.m.