Triple
T6164245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DU |
E137516
|
entity |
| Predicate | hasCollegesType |
P69155
|
FINISHED |
| Object | constituent colleges |
—
|
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 colleges | Statement: [DU, hasCollegesType, constituent colleges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollegesType Context triple: [DU, hasCollegesType, constituent colleges]
-
A.
hasAffiliatedCollegesIn
Indicates that an institution maintains affiliated colleges located within a specified geographic area or jurisdiction.
-
B.
hasCollegeType
Indicates that a college or educational institution is classified as having a specific type or category (e.g., public, private, community, technical).
-
C.
hasResidentialColleges
Indicates that an institution or organization includes one or more residential colleges as part of its structure or system.
-
D.
hasUniversities
Indicates that an entity possesses, contains, or is associated with one or more universities.
-
E.
hasCollegeCampus
Indicates that an institution or organization possesses or is associated with a specific college campus as a physical or organizational site.
- 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_69c008a54fc88190b6ce4416490ca79d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d6036f88190a4bf540e7fe8d48d |
completed | March 22, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69c055f5b81481908819515cdc334ae6 |
completed | March 22, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69c056df95ac8190bc5efe050d3af864 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:17 p.m.