Triple
T13534621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal sign-manual |
E323228
|
entity |
| Predicate | givesLegalForceTo |
P26796
|
FINISHED |
| Object | official documents |
—
|
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: official documents | Statement: [Royal sign-manual, givesLegalForceTo, official documents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: givesLegalForceTo Context triple: [Royal sign-manual, givesLegalForceTo, official documents]
-
A.
hasLegalForceIn
chosen
Indicates that something (such as a law, regulation, or agreement) is legally valid, binding, and enforceable within a specified jurisdiction or context.
-
B.
hasLegalForceFrom
Indicates that one legal instrument, decision, or norm derives its binding legal effect or enforceability from another specified source.
-
C.
hasLegalAuthorityFrom
Indicates that one entity possesses formal legal power, rights, or authorization that originates from or is granted by another entity.
-
D.
forcesAction
Indicates that one entity compels or coerces another entity to perform a specific action or behavior.
-
E.
forceAbility
Indicates that one entity has the power or capacity to compel, influence, or cause another entity to act or change in a particular way.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafbcad2881909fb7490311807f75 |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:44 p.m.