Triple
T5294839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Cup competitions |
E119826
|
entity |
| Predicate | commonFormat |
P130
|
FINISHED |
| Object | qualification phase and final tournament |
—
|
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: qualification phase and final tournament | Statement: [World Cup competitions, commonFormat, qualification phase and final tournament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonFormat Context triple: [World Cup competitions, commonFormat, qualification phase and final tournament]
-
A.
typicalUsageFormat
Indicates the usual or standard way in which something is expressed, presented, or formatted in practice.
-
B.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
C.
packageFormat
Indicates the format or type in which a package is structured, encoded, or delivered.
-
D.
exchangeFormat
Indicates that one entity uses, supports, or is represented in a particular data or communication format for exchanging information with another system or entity.
-
E.
relatedFormat
Indicates that two resources are available in different but closely related formats or media representations of essentially the same content.
- 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_69bd446f22b88190b6a47fb91c68a3e7 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8682d18c8190bbb35cc75c8a7c12 |
completed | March 20, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69bd844dfdac819086efedd1cbebff84 |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:52 p.m.