Triple
T15232539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BGBl. Nr. 1/1930 as amended |
E364039
|
entity |
| Predicate | promulgationCitation |
P4420
|
FINISHED |
| Object | BGBl. Nr. 1/1930 |
—
|
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: BGBl. Nr. 1/1930 | Statement: [BGBl. Nr. 1/1930 as amended, promulgationCitation, BGBl. Nr. 1/1930]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promulgationCitation Context triple: [BGBl. Nr. 1/1930 as amended, promulgationCitation, BGBl. Nr. 1/1930]
-
A.
promulgates
Indicates the act of formally declaring, publishing, or putting a law, rule, or doctrine into official effect.
-
B.
promulgatedFollowing
Indicates that one event, rule, or decision was formally announced or put into effect after, and as a consequence of, another event or condition.
-
C.
promulgationMethod
Indicates the method or process by which a law, rule, or official decision is formally announced or put into effect.
-
D.
promulgatedAt
Indicates the time or date at which an official rule, law, or document is formally issued or put into effect.
-
E.
legalCitation
chosen
Indicates that one legal document, case, or authority formally references or cites another as a source of legal support or precedent.
- 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.