Triple
T37972525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UTRGV Vaqueros |
E947327
|
entity |
| Predicate | formerInstitutionalLineage |
P129121
|
FINISHED |
| Object | UTPA Broncs |
—
|
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: UTPA Broncs | Statement: [UTRGV Vaqueros, formerInstitutionalLineage, UTPA Broncs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerInstitutionalLineage Context triple: [UTRGV Vaqueros, formerInstitutionalLineage, UTPA Broncs]
-
A.
parentInstitutionFormerName
Indicates that the parent institution of an entity previously operated under a different official name.
-
B.
hasFormerInstitution
Indicates that an entity was previously affiliated with, employed by, or enrolled in a particular institution in the past.
-
C.
hasFormerInstitutionName
Indicates that an institution was previously known by a different name.
-
D.
hasFormerInstitutionType
Indicates that an entity was previously associated with or classified under a particular type of institution.
-
E.
laterInstitutionKnownAs
chosen
Indicates that an institution was subsequently renamed or rebranded and is now known by a later institutional name.
- 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_69f76ef7db908190bba6086673a32300 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0127c36dc08190b07765756b3d0e1b |
completed | May 11, 2026, 12:50 a.m. |
| PD | Predicate disambiguation | batch_6a0125ef57208190be5b5e761fcae981 |
completed | May 11, 2026, 12:42 a.m. |
Created at: May 3, 2026, 4:20 p.m.