Triple
T3144038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Olympic Committee |
E65720
|
entity |
| Predicate | promotesEvent |
P1258
|
FINISHED |
| Object | Olympic Day activities in Canada |
—
|
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: Olympic Day activities in Canada | Statement: [Canadian Olympic Committee, promotesEvent, Olympic Day activities in Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotesEvent Context triple: [Canadian Olympic Committee, promotesEvent, Olympic Day activities in Canada]
-
A.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
B.
portraysEvent
Indicates that one entity depicts, represents, or illustrates a particular event.
-
C.
eventRole
Indicates the specific function, capacity, or part an entity plays within an event or occurrence.
-
D.
promotes
chosen
Indicates that one entity actively supports, advances, or encourages the growth, adoption, or success of another entity or outcome.
-
E.
featuresEvent
Indicates that an entity includes, presents, or highlights a particular event as part of its content or offering.
- 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_69ad8582f564819088c27e1f96153938 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada595d4548190b720a6131817833b |
completed | March 8, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfa3d9081908425aa636bb9b897 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.