Triple
T25875611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lindenwood Lions |
E651891
|
entity |
| Predicate | governsVarsitySports |
P182205
|
FINISHED |
| Object | Lindenwood University |
—
|
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: Lindenwood University | Statement: [Lindenwood Lions, governsVarsitySports, Lindenwood University]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsVarsitySports Context triple: [Lindenwood Lions, governsVarsitySports, Lindenwood University]
-
A.
governsNumberOfVarsityTeams
Indicates that one entity has authority over or control of how many varsity teams another entity has.
-
B.
athleticDirectorOversight
Indicates that an athletic director has supervisory authority or administrative oversight over a sports program, department, or related activities.
-
C.
universitySport
Indicates a relationship where a particular sport is officially associated with, offered, or organized by a university.
-
D.
universityAthleticDepartment
Indicates that a university has an associated athletic department that manages its sports programs and related activities.
-
E.
hasVarsityTeams
Indicates that an institution fields official varsity-level sports teams.
- 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_69e7ab3ad9d88190841ddcb93ab02e96 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7886b27f08190ab4580f949222c93 |
completed | May 3, 2026, 5:39 p.m. |
Created at: April 22, 2026, 8:12 a.m.