Triple
T28175827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argentina national football teams |
E715586
|
entity |
| Predicate | competitionFormats |
P2673
|
FINISHED |
| Object | 11-a-side football |
—
|
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: 11-a-side football | Statement: [Argentina national football teams, competitionFormats, 11-a-side football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionFormats Context triple: [Argentina national football teams, competitionFormats, 11-a-side football]
-
A.
competitionFormat
chosen
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
B.
teamSportFormat
Indicates the type or structure of how a sport is organized and played as a team-based competition.
-
C.
tourFormat
Indicates the specific structure, style, or type of a tour associated with an entity.
-
D.
playedFormat
Indicates that an entity (such as a game, show, or media content) is or was presented, delivered, or experienced in a particular format (such as digital, physical, live, or specific media type).
-
E.
careerFormat
Indicates the specific structure or type of professional path or occupational arrangement associated with an entity.
- 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 27, 2026, 10:16 p.m.