Triple
T4499915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concordia Stingers |
E101192
|
entity |
| Predicate | notableAlumniSport |
P4387
|
FINISHED |
| Object | CFL players |
—
|
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: CFL players | Statement: [Concordia Stingers, notableAlumniSport, CFL players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAlumniSport Context triple: [Concordia Stingers, notableAlumniSport, CFL players]
-
A.
notableAthlete
Indicates that the subject is a well-known or distinguished athlete associated with the object (such as a sport, team, or organization).
-
B.
hallOfFameAlumnus
Indicates that an individual is recognized as a Hall of Fame member associated with a particular institution, organization, or group.
-
C.
hasNotableAlumniType
chosen
Indicates that an entity has notable alumni belonging to a specified category or type.
-
D.
notableStudentBodyAssociatedWith
Indicates that there is a significant or noteworthy group of students associated with a particular entity, such as an institution, organization, or program.
-
E.
notableStudent
Indicates that a person is a distinguished or particularly significant student of another individual or institution.
- 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_69bd43d175248190894dc58b5b395c26 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56c4080c8190bd9580c961acaca8 |
completed | March 20, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1 p.m.