Triple
T7175887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuzla campus |
E167317
|
entity |
| Predicate | hostsDiscipline |
P25659
|
FINISHED |
| Object | engineering |
—
|
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 | Statement: [Tuzla campus, hostsDiscipline, engineering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostsDiscipline Context triple: [Tuzla campus, hostsDiscipline, engineering]
-
A.
hostedDiscipline
Indicates that an entity served as the host or venue for a particular discipline, event category, or field of competition.
-
B.
housesDiscipline
chosen
Indicates that one entity serves as the location, container, or institutional home for a particular discipline or field of study.
-
C.
supportsDiscipline
Indicates that one entity provides assistance, resources, or endorsement that helps sustain or advance a particular discipline.
-
D.
hasDisciplineSystem
Indicates that an entity possesses or is governed by a particular system of rules, methods, or practices for maintaining discipline.
-
E.
host
Indicates that one entity provides space, resources, or services to accommodate, receive, or entertain another entity.
- 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_69c68889a2748190a316c5e65360361a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e9b045c48190b27b2d6f7c11026f |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e74fb0f48190b2ad4dd4efdd241a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:48 p.m.