Triple
T13092520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antiguoko |
E310495
|
entity |
| Predicate | footballCode |
P50040
|
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: [Antiguoko, footballCode, 11-a-side football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: footballCode Context triple: [Antiguoko, footballCode, 11-a-side football]
-
A.
FIFAcode
Indicates the standardized three-letter country or territory code assigned by FIFA to represent a national football team in international competitions.
-
B.
gridironCode
Indicates the specific code or rule set of gridiron football (e.g., NFL, college, high school) that governs how the game is played in a given context.
-
C.
footballBowlSubdivision
Indicates that a college football team competes in the NCAA Football Bowl Subdivision (FBS) level.
-
D.
nationalFootballTeam
Indicates that one entity is the official football (soccer) team representing the other entity at the national level.
-
E.
sportCode
chosen
Indicates the specific sport associated with or classified for an entity, typically via a standardized code or identifier.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9813acbac8190b2fe5e07287457cf |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:03 p.m.