Triple
T28772691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victor Boin |
E726453
|
entity |
| Predicate | tookOlympicOathInCity |
P16887
|
FINISHED |
| Object | Antwerp |
—
|
NE NERFINISHED |
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: Antwerp | Statement: [Victor Boin, tookOlympicOathInCity, Antwerp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookOlympicOathInCity Context triple: [Victor Boin, tookOlympicOathInCity, Antwerp]
-
A.
olympicOathByOfficial
Indicates that an Olympic official formally delivers the Olympic Oath on behalf of all officials at the Games.
-
B.
OlympicOathYear
Indicates the year in which the Olympic Oath was taken or delivered at a particular edition of the Olympic Games.
-
C.
athletesOathBy
chosen
Indicates that an athlete’s oath is formally delivered or performed by a specific person or group.
-
D.
OlympicOathSeason
Indicates the season (e.g., Summer or Winter) of the Olympic Games at which a particular Olympic Oath was taken.
-
E.
representedAtOlympics
Indicates that an entity served as an official representative (e.g., athlete, team, or delegation) for another entity at a specific edition of the Olympic Games.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 6:16 a.m.