Triple
T34259068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cougars |
E878974
|
entity |
| Predicate | governingBodyFormer |
P203058
|
FINISHED |
| Object | NAIA |
—
|
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: NAIA | Statement: [Cougars, governingBodyFormer, NAIA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingBodyFormer Context triple: [Cougars, governingBodyFormer, NAIA]
-
A.
governingBodyPreviouslyKnownAs
Indicates that the governing body currently associated with an entity was formerly known by a different name.
-
B.
governingBodyLaterKnownAs
Indicates that the governing body of an entity was later renamed or became known by a different official title.
-
C.
governingBodyDuringExistence
Indicates that a specific governing body had authority over or administered an entity throughout the period of that entity’s existence.
-
D.
previousGoverningBody
Indicates that one governing body served in authority immediately before another specified governing body.
-
E.
governingBodyAfter
Indicates that one governing body succeeds another as the official authority over the same entity or jurisdiction.
- 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_69f349b421cc8190b4b4655e1d612548 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0119132e848190820a688d139fbf75 |
completed | May 10, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_6a01188dfdec8190b7f675264a281733 |
completed | May 10, 2026, 11:45 p.m. |
| PDg | Predicate description generation | batch_6a0119127ca481909e921e7d95716b00 |
completed | May 10, 2026, 11:47 p.m. |
Created at: May 1, 2026, 1:56 a.m.