Triple
T7827503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIFA World Cup South American qualifiers |
E181282
|
entity |
| Predicate | usesFIFALawsOfTheGame |
P6601
|
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: [FIFA World Cup South American qualifiers, usesFIFALawsOfTheGame, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFIFALawsOfTheGame Context triple: [FIFA World Cup South American qualifiers, usesFIFALawsOfTheGame, true]
-
A.
playedUnderRulesOf
chosen
Indicates that an activity or game was conducted in accordance with a specified set of rules or regulations.
-
B.
usesAmericanRules
Indicates that the action, process, or system is conducted according to American rules or standards rather than other rule sets.
-
C.
usesNumberOfPlayersOnFieldPerTeam
Indicates that the relationship specifies or depends on how many players each team has on the field at a given time.
-
D.
hasRulebook
Indicates that one entity possesses, is governed by, or is associated with a specific rulebook.
-
E.
FIFAcode
Indicates the standardized three-letter country or territory code assigned by FIFA to represent a national football team in international competitions.
- 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_69ca8282ccec819083c48efb72d21cf9 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb04a97d748190b1924890b1328bf1 |
completed | March 30, 2026, 11:18 p.m. |
| PD | Predicate disambiguation | batch_69cae91ae008819098e56bbe51143b31 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:43 p.m.