Triple
T37627376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Führerprinzip |
E936246
|
entity |
| Predicate | legalEmbedding |
P201597
|
FINISHED |
| Object | Enabling Act of 1933 |
—
|
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: Enabling Act of 1933 | Statement: [Führerprinzip, legalEmbedding, Enabling Act of 1933]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalEmbedding Context triple: [Führerprinzip, legalEmbedding, Enabling Act of 1933]
-
A.
legalCorpus
Indicates that an entity is part of, contained in, or belongs to a body of legal texts, statutes, or case law used as a legal corpus.
-
B.
legalTool
Indicates a relationship where something functions as a legal instrument, mechanism, or means used to achieve or regulate a legal purpose or outcome.
-
C.
legalElement
Indicates that something is a constituent part or component required or recognized within a legal framework, rule, or process.
-
D.
legalOutput
Indicates that an action, process, or system produces results or consequences that are compliant with applicable laws or legal standards.
-
E.
legalContent
Indicates that the associated material complies with applicable laws and regulations and is permitted for use, distribution, or display.
- 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a000a1d8fa88190a1d82ac746565c48 |
completed | May 10, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_6a0008b26eb88190ae03b2309a614774 |
completed | May 10, 2026, 4:25 a.m. |
| PDg | Predicate description generation | batch_6a000a1c8f8881908293ab4f7207d25f |
completed | May 10, 2026, 4:31 a.m. |
Created at: May 3, 2026, 4:18 p.m.