Triple
T27869889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITA |
E704462
|
entity |
| Predicate | usedInQualificationMatches |
P180855
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [ITA, usedInQualificationMatches, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInQualificationMatches Context triple: [ITA, usedInQualificationMatches, yes]
-
A.
usesQualificationSystem
Indicates that an entity applies or relies on a specific qualification system as part of its processes or operations.
-
B.
playsQualificationMatches
Indicates that an entity participates in qualification matches, typically as part of a preliminary stage to qualify for a main event or competition.
-
C.
usedForPlayoffQualification
Indicates that something serves as a basis or criterion for determining whether a team qualifies for the playoffs.
-
D.
hasQualifyingRounds
Indicates that an event or competition includes preliminary qualifying rounds that participants must complete before advancing further.
-
E.
usedInTournamentDraws
chosen
Indicates that something (such as a rule, method, or system) is employed when constructing or organizing the draws for a tournament.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 27, 2026, 6:23 p.m.