Triple
T1191248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vienna University of Economics and Business |
E25364
|
entity |
| Predicate | campusCharacteristic |
P2465
|
FINISHED |
| Object | modern campus architecture |
—
|
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: modern campus architecture | Statement: [Vienna University of Economics and Business, campusCharacteristic, modern campus architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campusCharacteristic Context triple: [Vienna University of Economics and Business, campusCharacteristic, modern campus architecture]
-
A.
cityCampus
Indicates that a campus is located within or associated with a particular city.
-
B.
campusType
Indicates the classification or category of a campus based on its type (e.g., main, satellite, urban, rural).
-
C.
hasCampusFeature
chosen
Indicates that a campus possesses or includes a specific physical or functional feature.
-
D.
campusLandmark
Indicates that something serves as a notable or recognizable landmark located on or associated with a campus.
-
E.
campus
Indicates that an entity is located on, associated with, or taking place within a particular campus.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd74e2c08190b4a48425f94addaa |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5bacc481909e8dfd5215e4711a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.