Triple
T26565591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordic combined at the 2010 Winter Olympics |
E666371
|
entity |
| Predicate | isTeamEventIncluded |
P160643
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nordic combined at the 2010 Winter Olympics, isTeamEventIncluded, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTeamEventIncluded Context triple: [Nordic combined at the 2010 Winter Olympics, isTeamEventIncluded, true]
-
A.
includesEvents
Indicates that one entity contains or encompasses one or more events as part of its scope or composition.
-
B.
includesTeam
Indicates that a group, project, or organization has a specific team as one of its constituent members or components.
-
C.
includesInvitedTeams
Indicates that certain teams are explicitly included as invited participants in an event, activity, or context.
-
D.
includesTeamsThat
Indicates that an entity contains or encompasses specific teams as part of its composition or scope.
-
E.
participationIncludes
Indicates that a broader participation instance encompasses or contains a more specific participation instance as part of it.
- 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_69ee9cf7e94481909f0d556b36e43572 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6149de5408190803077b6ef97b8f7 |
completed | May 2, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 27, 2026, 1:55 a.m.