Triple
T32366027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redmen |
E826992
|
entity |
| Predicate | usedByAthleticAssociation |
P188116
|
FINISHED |
| Object | NCAA |
—
|
NE NERFINISHED |
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: NCAA | Statement: [Redmen, usedByAthleticAssociation, NCAA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByAthleticAssociation Context triple: [Redmen, usedByAthleticAssociation, NCAA]
-
A.
usedInSport
Indicates that something (such as an object, technique, or concept) is employed or utilized within the context of a particular sport.
-
B.
athleticAssociationAbbreviation
Indicates the abbreviated form of the name of an athletic association with which an entity is affiliated.
-
C.
competesInAssociation
Indicates that an entity participates as a competitor within a specified association, league, or organized competitive body.
-
D.
sportingAssociation
Indicates a formal relationship in which an organization serves as a governing, organizing, or affiliating body for sports activities, teams, or events.
-
E.
usedByClub
Indicates that something (such as a resource, facility, or item) is utilized or employed by a club.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fba28684208190921694f23e350c3b |
completed | May 6, 2026, 8:20 p.m. |
Created at: May 1, 2026, 12:50 a.m.