Triple
T12464222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CELC |
E297878
|
entity |
| Predicate | holdsMeetingType |
P95912
|
FINISHED |
| Object | triennial convention |
—
|
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: triennial convention | Statement: [CELC, holdsMeetingType, triennial convention]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holdsMeetingType Context triple: [CELC, holdsMeetingType, triennial convention]
-
A.
meetsType
Indicates that one entity encounters or comes into contact with another entity in a particular manner or context.
-
B.
meetsEvery
Indicates that one entity encounters or comes into contact with every member of a specified set of entities.
-
C.
meetsTo
Indicates that one entity comes together with another at a specific time and place for an encounter, appointment, or interaction.
-
D.
hasConferenceType
chosen
Indicates that an entity is associated with or classified by a specific type or category of conference.
-
E.
meetsAs
Indicates that two entities encounter or come together at the same place and time, typically in a planned or recognized interaction.
- 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_69d6ada270808190b1a2b2e7b02bb426 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e626dbc8190ac7dcdb542ba9b0c |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d3f701c81909dd0e00251ac8553 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.