Triple
T29156940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babenberg territories in Austria |
E739073
|
entity |
| Predicate | elevationInstrument |
P176321
|
FINISHED |
| Object | Privilegium Minus |
—
|
NE NERFINISHED |
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: Privilegium Minus | Statement: [Babenberg territories in Austria, elevationInstrument, Privilegium Minus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationInstrument Context triple: [Babenberg territories in Austria, elevationInstrument, Privilegium Minus]
-
A.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
B.
elevationDeterminedIn
Indicates that the elevation of an entity is established or measured within a specific context, process, or event.
-
C.
elevationBy
Indicates a relationship where one entity raises, increases, or enhances the level, status, or intensity of another entity.
-
D.
elevationHolder
Indicates that one entity serves as the reference or container for the elevation (height above a baseline) associated with another entity.
-
E.
elevationType
Indicates the kind or classification of elevation associated with an entity, such as how its height or altitude is characterized.
- F. None of above. chosen
Provenance (4 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_69f07cb528fc8190a556b73990c347c8 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6dfcafd0c81908d86662948c539d6 |
completed | May 3, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6df418f488190a5e7ff41f32dceda |
completed | May 3, 2026, 5:38 a.m. |
Created at: April 28, 2026, 11:45 a.m.