Triple
T28390340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GV |
E719136
|
entity |
| Predicate | refersToInstitutionCategory |
P58498
|
FINISHED |
| Object | university |
—
|
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: university | Statement: [GV, refersToInstitutionCategory, university]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToInstitutionCategory Context triple: [GV, refersToInstitutionCategory, university]
-
A.
hasInstitutionalCategory
chosen
Indicates that an entity is classified under a specific institutional type or category within an organizational or institutional framework.
-
B.
recognizedAsInstitutionBy
Indicates that an entity is acknowledged or accepted as an institution by a specified recognizing party.
-
C.
inInstitution
Indicates that an entity is located within, belongs to, or is formally associated with a particular institution.
-
D.
associatedInstitutionType
Indicates the type or category of institution with which an entity is associated.
-
E.
involvesInstitution
Indicates that an action, event, or relationship includes or is associated with an institution as a participating party.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 28, 2026, 1:13 a.m.