Triple
T30114361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1998 FIFA World Cup qualification |
E765371
|
entity |
| Predicate | qualificationFormatFeature |
P167790
|
FINISHED |
| Object | group stage |
—
|
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: group stage | Statement: [1998 FIFA World Cup qualification, qualificationFormatFeature, group stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualificationFormatFeature Context triple: [1998 FIFA World Cup qualification, qualificationFormatFeature, group stage]
-
A.
competitionFormat
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
B.
qualificationHeld
Indicates that an entity possesses or has obtained a particular qualification or credential.
-
C.
careerFormat
Indicates the specific structure or type of professional path or occupational arrangement associated with an entity.
-
D.
qualifyingRoundFormat
chosen
Indicates the specific structure or rules used to organize and conduct a qualifying round in a competition or event.
-
E.
qualifyingFor
Indicates that one entity meets the necessary conditions or criteria to be eligible for another entity, status, or action.
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 29, 2026, 7:11 p.m.