Triple
T744119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgian monarchy |
E15303
|
entity |
| Predicate | promulgatesLaws |
P1115
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Belgian monarchy, promulgatesLaws, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promulgatesLaws Context triple: [Belgian monarchy, promulgatesLaws, yes]
-
A.
passedLegislation
Indicates that a governing body has formally approved and enacted a specific piece of legislation or law.
-
B.
enactedBy
chosen
Indicates that a law, policy, or formal measure is officially established or brought into effect by a specific authority or governing body.
-
C.
legalAct
Indicates that an entity performs, enacts, or is involved in a formal legal action, measure, or proceeding under a legal framework.
-
D.
areaOfLegislation
Indicates that one entity defines, concerns, or governs the legal domain or subject matter covered by another entity.
-
E.
legislativeArticle
Indicates a relationship where one entity is a specific article or clause within a legislative or legal document that governs or regulates another entity.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a610ba9881908b4e5e7dcc6ed0f5 |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a4ff10608190bfd60b4a1cb38f7d |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.