Triple
T20884310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Univ |
E514233
|
entity |
| Predicate | hasCollegiateStatus |
P63066
|
FINISHED |
| Object | constituent 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: constituent college | Statement: [Univ, hasCollegiateStatus, constituent college]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollegiateStatus Context triple: [Univ, hasCollegiateStatus, constituent college]
-
A.
collegiateStatus
chosen
Indicates the relationship between an entity and a college or university, specifying its status or standing within that academic institution (e.g., enrolled, graduated, affiliated).
-
B.
isCollegiate
Indicates that an entity is associated with or participates in a college-level institution, program, or context.
-
C.
isInCollege
Indicates that a person is currently enrolled as a student at a college or university.
-
D.
isCollegiateLeague
Indicates that a sports league operates at the college or university level, involving teams representing academic institutions.
-
E.
formerMajorCollegeStatus
Indicates that an entity previously held, but no longer holds, the status of being a major college.
- 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c67bd32c819097301e330e358c49 |
completed | April 21, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:46 p.m.