Triple
T1330703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana University–Purdue University Indianapolis |
E28636
|
entity |
| Predicate | isUrbanUniversity |
P27290
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Indiana University–Purdue University Indianapolis, isUrbanUniversity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUrbanUniversity Context triple: [Indiana University–Purdue University Indianapolis, isUrbanUniversity, true]
-
A.
universityLocatedIn
Indicates that a university is situated within or associated with a specific geographic location or administrative region.
-
B.
hasPublicUniversityCampus
Indicates that a public university maintains or operates a campus at the specified location.
-
C.
isResearchUniversity
Indicates that an institution functions primarily as a research-focused university, emphasizing the creation of new knowledge alongside advanced education.
-
D.
cityCampus
Indicates that a campus is located within or associated with a particular city.
-
E.
isPublicUniversityCampus
Indicates that a given campus belongs to and is operated as part of a public (state- or government-funded) university.
- F. None of above. chosen
Provenance (4 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1c449bc8190acb6603a0ddac7fd |
completed | March 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69a4beef6a188190996f8775bdda8f6c |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c0b1326081909aa6beec0cfe8d6c |
completed | March 1, 2026, 10:41 p.m. |
Created at: March 1, 2026, 7:55 p.m.