Triple
T8811487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian national cross-country skiing team |
E209672
|
entity |
| Predicate | isEliteTeam |
P37488
|
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: [Italian national cross-country skiing team, isEliteTeam, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEliteTeam Context triple: [Italian national cross-country skiing team, isEliteTeam, true]
-
A.
isEliteUnit
chosen
Indicates that the unit belongs to a specially trained, highly capable subgroup distinguished from regular units.
-
B.
isTeamSpecific
Indicates that something applies only to, or is restricted to, a particular team rather than being general or shared across multiple teams.
-
C.
containsSportsTeam
Indicates that one entity (typically a location or organization) has a sports team as part of it or within its boundaries.
-
D.
teamEligibility
Indicates whether an entity meets the required conditions to participate as a member of a particular team.
-
E.
qualifiedTeam
Indicates that a team has met the necessary criteria or achieved the required results to advance or be accepted into a particular stage, event, or competition.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fed18f8819087b0282bf8c4208c |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.