Triple
T17503594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McLennan Community College |
E426253
|
entity |
| Predicate | institutionalCategory |
P58498
|
FINISHED |
| Object | two-year college |
—
|
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: two-year college | Statement: [McLennan Community College, institutionalCategory, two-year college]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: institutionalCategory Context triple: [McLennan Community College, institutionalCategory, two-year college]
-
A.
institutionCategory
Indicates the classification or type of institution to which an entity belongs (e.g., university, hospital, bank).
-
B.
hasInstitutionalCategory
chosen
Indicates that an entity is classified under a specific institutional type or category within an organizational or institutional framework.
-
C.
institutionalPurpose
Indicates the intended function, mission, or role that an institution is designed or established to fulfill.
-
D.
inInstitution
Indicates that an entity is located within, belongs to, or is formally associated with a particular institution.
-
E.
typeOfInstitution
Indicates the specific kind or category of institution that an entity belongs to or is classified as.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e45213a0e88190ac183d87ec088e86 |
completed | April 19, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.