Triple
T7595561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G5 group |
E179848
|
entity |
| Predicate | memberUniversitiesType |
P29027
|
FINISHED |
| Object | research-intensive universities |
—
|
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: research-intensive universities | Statement: [G5 group, memberUniversitiesType, research-intensive universities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberUniversitiesType Context triple: [G5 group, memberUniversitiesType, research-intensive universities]
-
A.
hasAffiliatedCollegesIn
Indicates that an institution maintains affiliated colleges located within a specified geographic area or jurisdiction.
-
B.
associatedInstitutionType
chosen
Indicates the type or category of institution with which an entity is associated.
-
C.
hasUniversities
Indicates that an entity possesses, contains, or is associated with one or more universities.
-
D.
associatedInstitution
Indicates that an entity has a formal connection or affiliation with a particular institution.
-
E.
universityOrganizationType
Indicates the specific organizational category or classification of a university (such as public, private, or other institutional type).
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9d39e9481908bec42447c97e3f8 |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:53 p.m.