Triple
T254870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Parliament |
E5414
|
entity |
| Predicate | requiresRoyalAssent |
P8959
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [British Parliament, requiresRoyalAssent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresRoyalAssent Context triple: [British Parliament, requiresRoyalAssent, true]
-
A.
ratifiedBy
Indicates that an agreement, treaty, or decision has been formally approved and made officially valid by a specified authority or body.
-
B.
ratificationMethod
Indicates the process or formal procedure by which an agreement, decision, or document is officially approved and made valid.
-
C.
passedLegislation
Indicates that a governing body has formally approved and enacted a specific piece of legislation or law.
-
D.
ratificationVote
Indicates a formal vote taken to approve, confirm, or give official sanction to a decision, agreement, or action.
-
E.
requiresDomesticLegislation
Indicates that the fulfillment, implementation, or enforcement of one entity depends on the adoption or existence of specific domestic legislation by another entity (typically a state or jurisdiction).
- 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25d548cac819081b1636b2a057c62 |
completed | Feb. 28, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69a25b694c08819085bb4b256fa7736f |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c4b773c81908f1017f40b0bfd07 |
completed | Feb. 28, 2026, 3:08 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.