Triple
T15232565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BGBl. Nr. 1/1930 as amended |
E364039
|
entity |
| Predicate | hasNormHierarchyLevel |
P2393
|
FINISHED |
| Object | constitution |
—
|
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: constitution | Statement: [BGBl. Nr. 1/1930 as amended, hasNormHierarchyLevel, constitution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNormHierarchyLevel Context triple: [BGBl. Nr. 1/1930 as amended, hasNormHierarchyLevel, constitution]
-
A.
hasNumberOfLevels
Indicates that an entity possesses a specified count of distinct levels or tiers.
-
B.
hasNorm
Indicates that an entity is associated with, governed by, or characterized through a particular norm, rule, or standard.
-
C.
hasLevelNumber
Indicates that an entity is associated with a specific level identified by a numerical value.
-
D.
hasHierarchyIn
Indicates that one entity occupies a higher or lower level within an ordered structure or chain of command relative to another entity in a specified context.
-
E.
hasLevel
chosen
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007d7237081908dc17900ee66b64f |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:12 a.m.