Triple
T32456585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic 10 Player of the Year |
E829443
|
entity |
| Predicate | hasConferenceAbbreviation |
P8075
|
FINISHED |
| Object | A-10 |
E202155
|
NE 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: A-10 | Statement: [Atlantic 10 Player of the Year, hasConferenceAbbreviation, A-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConferenceAbbreviation Context triple: [Atlantic 10 Player of the Year, hasConferenceAbbreviation, A-10]
-
A.
hasConferenceCode
Indicates that a conference is associated with a specific identifying code.
-
B.
hasConferenceSport
Indicates that an institution participates in or is associated with a particular sport within a specific athletic conference.
-
C.
hasConference
Indicates that an entity organizes, hosts, or is associated with a specific conference.
-
D.
hasConferenceOrDivision
Indicates that an entity is associated with a specific conference or division within a larger organizational or competitive structure.
-
E.
hasNameAbbreviation
chosen
Indicates that an entity is associated with a shortened or abbreviated form of its full name.
- F. None of above.
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_69f3491df9288190afc0b23b1d6e72ce |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34668db8748190b970ca9ee5be762b |
completed | June 18, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:56 a.m.