Triple
T14015633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | modern pentathlon |
E337196
|
entity |
| Predicate | introducedCombinedEvent |
P110108
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [modern pentathlon, introducedCombinedEvent, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedCombinedEvent Context triple: [modern pentathlon, introducedCombinedEvent, 2009]
-
A.
introducedEvent
Indicates that an entity is responsible for bringing an event into existence or initiating it for the first time.
-
B.
firstHeldAsCombinedEvent
chosen
Indicates that an event was held for the first time as a combined or joint occurrence, rather than as separate events.
-
C.
introductionEvent
Indicates an event in which one entity is formally presented or made known to another entity or audience for the first time.
-
D.
introducedAlongWith
Indicates that one entity was introduced or presented at the same time as another entity, as part of a joint or concurrent introduction.
-
E.
introduced
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f396b648190927e5718c3bb6511 |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.