Triple
T22150773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EMS Prize |
E547405
|
entity |
| Predicate | ceremonyLocationType |
P147182
|
FINISHED |
| Object | European Congress of Mathematics host city |
—
|
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: European Congress of Mathematics host city | Statement: [EMS Prize, ceremonyLocationType, European Congress of Mathematics host city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonyLocationType Context triple: [EMS Prize, ceremonyLocationType, European Congress of Mathematics host city]
-
A.
ceremonyLocation
Indicates the place where a ceremony is held or takes place.
-
B.
ceremonyType
Indicates the specific kind or category of ceremony associated with an event or relationship.
-
C.
ceremonyHeld
Indicates that a formal ceremony or ritual event has taken place at a particular time and/or location.
-
D.
ceremonyHeldNear
Indicates that a ceremony takes place at a location that is geographically close to a specified reference place or object.
-
E.
ceremonialVenueFunction
Indicates that a venue serves a role or purpose specifically related to hosting or supporting ceremonial events or activities.
- 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129f37dac8190a7cecb12f4271515 |
completed | April 28, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:33 p.m.