Triple
T30015176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faculty of Arts, Psychology and Theology |
E762574
|
entity |
| Predicate | multidisciplinary |
P18353
|
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: [Faculty of Arts, Psychology and Theology, multidisciplinary, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: multidisciplinary Context triple: [Faculty of Arts, Psychology and Theology, multidisciplinary, true]
-
A.
isMultidisciplinary
chosen
Indicates that something involves or integrates multiple distinct academic or professional disciplines in its approach or composition.
-
B.
mixedDiscipline
Indicates that an entity involves or combines multiple distinct disciplines, fields, or areas of expertise within a single context or activity.
-
C.
disciplinaryEmphasis
Indicates the primary academic or professional discipline that is emphasized or focused on within a given context.
-
D.
disciplinaryMethod
Indicates a method or approach used to discipline, correct, or control another party’s behavior.
-
E.
multiInstitutional
Indicates that an activity, project, or relationship involves participation or collaboration among multiple institutions.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 6:45 p.m.