Triple
T27970111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Joy of Data |
E706329
|
entity |
| Predicate | hasPresenterOccupation |
P72070
|
FINISHED |
| Object | mathematician |
—
|
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: mathematician | Statement: [The Joy of Data, hasPresenterOccupation, mathematician]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPresenterOccupation Context triple: [The Joy of Data, hasPresenterOccupation, mathematician]
-
A.
presenterOccupation
chosen
Indicates that an entity serves in a specific professional role or job as a presenter.
-
B.
hasNotablePortrayerOccupation
Indicates that the occupation specified is a notable profession of a person who portrays the given entity (such as an actor playing a character).
-
C.
hasPresentation
Indicates that an entity delivers, contains, or is associated with a specific presentation (such as a talk, slide deck, or formal display of information).
-
D.
hasPresenterType
Indicates the specific role or category of presenter associated with an event, item, or presentation.
-
E.
holderIsOccupation
Indicates that the holder entity has the specified occupation or job role.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fe831c97c88190b27ecf100e25c2a0 |
completed | May 9, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69fe7f1b92648190b14e56bcaee5d0ca |
completed | May 9, 2026, 12:26 a.m. |
Created at: April 27, 2026, 7:37 p.m.