Triple
T2713074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGA |
E59905
|
entity |
| Predicate | usedInTournamentAbbreviations |
P42511
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [NGA, usedInTournamentAbbreviations, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInTournamentAbbreviations Context triple: [NGA, usedInTournamentAbbreviations, yes]
-
A.
abbreviationUsedFor
Indicates that a particular shortened form or acronym is used to represent or stand in for a longer term, name, or expression.
-
B.
usedInPlayByPlayFor
Indicates that something (such as data, terminology, or a resource) is utilized within the context of a play-by-play account or commentary.
-
C.
usedInLeague
Indicates that an entity (such as a team, player, or item) participates or is employed within a particular league.
-
D.
abbreviationOfTeam
Indicates that one term is an abbreviation or shortened form of a team’s full name.
-
E.
usedInSport
Indicates that something (such as an object, technique, or concept) is employed or utilized within the context of a particular sport.
- F. None of above. chosen
Provenance (4 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_69ab4ac92a088190bc74bca14038e3de |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda924b24819090adc4128e86d4bd |
completed | March 7, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69abd8224c688190bb4a362360b03007 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8abcc348190bfa05c0abc4bcee7 |
completed | March 7, 2026, 7:50 a.m. |
Created at: March 6, 2026, 9:55 p.m.