Triple
T2035938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arts & Sciences |
E44627
|
entity |
| Predicate | hasDepartmentType |
P658
|
FINISHED |
| Object | humanities department |
—
|
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: humanities department | Statement: [Arts & Sciences, hasDepartmentType, humanities department]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDepartmentType Context triple: [Arts & Sciences, hasDepartmentType, humanities department]
-
A.
departmentType
chosen
Indicates the classification or category of a department, specifying what kind of department it is.
-
B.
hasAffiliationType
Indicates that one entity is connected to another through a specified kind or category of affiliation or association.
-
C.
hasAcademicDepartment
Indicates that an institution or organization includes or is associated with a specific academic department.
-
D.
hasFacultyType
Indicates that a faculty member or academic unit is associated with a specific category or type of faculty (e.g., full-time, adjunct, visiting).
-
E.
hasCommitteeType
Indicates that an entity is associated with a committee of a specified type or classification.
- 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_69a889159ec481908f9e4472d9f480c7 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb934ff948190acd88d4f587463a4 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.