Triple
T768957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | School of Humanities and Sciences |
E16237
|
entity |
| Predicate | encompassesDiscipline |
P18030
|
FINISHED |
| Object | arts |
—
|
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: arts | Statement: [School of Humanities and Sciences, encompassesDiscipline, arts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encompassesDiscipline Context triple: [School of Humanities and Sciences, encompassesDiscipline, arts]
-
A.
associatedWithDiscipline
Indicates that an entity has a relevant connection or involvement with a particular academic, professional, or thematic discipline.
-
B.
subDisciplineOf
Indicates that one discipline is a more specialized or narrower field within another, broader discipline.
-
C.
supportsDiscipline
Indicates that one entity provides assistance, resources, or endorsement that helps sustain or advance a particular discipline.
-
D.
hasSubdiscipline
Indicates that one discipline includes another, more specialized field of study as a subordinate branch.
-
E.
featuredDiscipline
chosen
Indicates that one discipline is highlighted or given special prominence in relation to another entity or context.
- 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a701e584819095905cf74d33e11c |
completed | March 1, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69a4a508c42c8190850a0ac7844a3ea9 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.