Triple
T30780819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athletics won 4–2 |
E783805
|
entity |
| Predicate | championAbbreviation |
P112542
|
FINISHED |
| Object | PHA |
—
|
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: PHA | Statement: [Athletics won 4–2, championAbbreviation, PHA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championAbbreviation Context triple: [Athletics won 4–2, championAbbreviation, PHA]
-
A.
championConferenceAffiliation
Indicates a relationship where a champion (e.g., a winning team or individual) is associated with the conference or league in which they achieved that championship.
-
B.
teamNicknameChampion
Indicates that a particular nickname is used to refer to a team that has achieved champion status in a competition or league.
-
C.
abbreviationOfTeam
Indicates that one term is an abbreviation or shortened form of a team’s full name.
-
D.
winnerAbbreviation
chosen
Indicates the abbreviated form or short code used to represent the winner in a given context or event.
-
E.
championOf
Indicates that one entity serves as the primary defender, advocate, or leading supporter of another entity, often working to promote or protect its interests.
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 29, 2026, 8:41 p.m.