Triple
T1964281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBE |
E42652
|
entity |
| Predicate | monarchApprovalRequired |
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: [CBE, monarchApprovalRequired, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monarchApprovalRequired Context triple: [CBE, monarchApprovalRequired, true]
-
A.
requiresRoyalAssent
chosen
Indicates that an action, decision, or legislative measure must receive formal approval from a monarch or royal representative before it becomes valid or effective.
-
B.
monarchUntil
Indicates that an entity served as monarch over another entity up to, but not beyond, a specified end time or event.
-
C.
supportedMonarch
Indicates that one entity actively backed, endorsed, or maintained the rule or authority of a particular monarch.
-
D.
requiresAdviceAndApprovalOf
Indicates that one entity can proceed with an action or decision only if it first seeks guidance and obtains formal approval from another entity.
-
E.
requiresMinisterialCountersignature
Indicates that an action, decision, or document is not valid or effective unless it is formally countersigned by a responsible minister.
- 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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3ada4148190ad830d4a3d7fd662 |
completed | March 7, 2026, 5:12 a.m. |
| PD | Predicate disambiguation | batch_69abaff7d4a48190ab0d51aefb1c4e31 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.