Triple
T5722342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TU9 |
E126174
|
entity |
| Predicate | hasDisciplineFocus |
P592
|
FINISHED |
| Object | engineering sciences |
—
|
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: engineering sciences | Statement: [TU9, hasDisciplineFocus, engineering sciences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisciplineFocus Context triple: [TU9, hasDisciplineFocus, engineering sciences]
-
A.
supportsDiscipline
Indicates that one entity provides assistance, resources, or endorsement that helps sustain or advance a particular discipline.
-
B.
hasSubdiscipline
Indicates that one discipline includes another, more specialized field of study as a subordinate branch.
-
C.
associatedWithDiscipline
chosen
Indicates that an entity has a relevant connection or involvement with a particular academic, professional, or thematic discipline.
-
D.
hasPrimaryDisciplineStructure
Indicates that an entity is associated with its main or principal organizational or structural form of discipline.
-
E.
governingDiscipline
Indicates that one discipline or field provides the primary rules, principles, or framework that regulate or guide another activity, domain, or practice.
- 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_69c0082e3d548190950169847b43043b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c47f4c81909e6849c3be3e951c |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:46 p.m.