Triple
T16927612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Transport Forum |
E410615
|
entity |
| Predicate | firstAnnualSummitHeld |
P91014
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [International Transport Forum, firstAnnualSummitHeld, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAnnualSummitHeld Context triple: [International Transport Forum, firstAnnualSummitHeld, 2008]
-
A.
firstSummitDate
Indicates the calendar date on which an entity (such as a person or team) first reached the summit of a particular peak or completed its initial summit ascent.
-
B.
firstInPersonLeadersSummitYear
chosen
Indicates the year in which the first in-person leaders’ summit for a given context or organization took place.
-
C.
firstSummitParty
Indicates the group of climbers or expedition members who first successfully reached the summit of a particular peak.
-
D.
firstEditionHeldIn
Indicates the location where the first edition or initial occurrence of an event was held.
-
E.
firstSessionHeldIn
Indicates that the initial or inaugural session of an event, activity, or process took place in a specified location 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cdf3fc3c8190a884f7ecd5c47adb |
completed | April 18, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.