Triple
T828016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Assent |
E17898
|
entity |
| Predicate | UKFormalPhrase |
P19806
|
FINISHED |
| Object | La Reyne le veult |
—
|
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: La Reyne le veult | Statement: [Royal Assent, UKFormalPhrase, La Reyne le veult]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UKFormalPhrase Context triple: [Royal Assent, UKFormalPhrase, La Reyne le veult]
-
A.
formalFunction
Indicates that an entity serves an official or designated role or purpose within a formal structure, system, or context.
-
B.
formalityLevel
Indicates the degree of social or stylistic formality characterizing an interaction, expression, or context between entities.
-
C.
traditionalCourtesyTitleHeir
Indicates that one entity holds the customary or historically recognized courtesy title associated with being the heir of another entity.
-
D.
formed
Indicates that one entity came into existence, shape, or organization as a result of the actions or processes involving another entity.
-
E.
formalContent
chosen
Indicates that the content is expressed in a formal, structured, or official manner, as opposed to casual or informal expression.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ab99b1e48190afad1f073348b29a |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa79a6488190a634388e071ed9b7 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.