Triple
T25651787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regents |
E643119
|
entity |
| Predicate | hasHomeInstitutionState |
P79153
|
FINISHED |
| Object | Illinois |
—
|
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: Illinois | Statement: [Regents, hasHomeInstitutionState, Illinois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeInstitutionState Context triple: [Regents, hasHomeInstitutionState, Illinois]
-
A.
hasStateInstitution
Indicates that a particular state possesses, governs, or is served by a specific institution operating under its authority or within its jurisdiction.
-
B.
hasHomeProvinceOrState
chosen
Indicates that an entity is associated with a particular province or state as its home or primary regional location.
-
C.
hasInstitutionalHome
Indicates that an entity is formally based in, hosted by, or affiliated with a particular institution as its organizational home.
-
D.
hasLocalInstitution
Indicates that a given place or region possesses or hosts an institution that operates locally within its boundaries.
-
E.
hasStateOrDistrict
Indicates that an entity is associated with, located in, or belongs to a particular state or district.
- 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_69e77e7d8a848190a98d0162325fd780 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 21, 2026, 6:25 p.m.