Triple
T10430374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mise of Amiens |
E245895
|
entity |
| Predicate | legalEffectOnKing |
P93546
|
FINISHED |
| Object | royal prerogatives reaffirmed |
—
|
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: royal prerogatives reaffirmed | Statement: [Mise of Amiens, legalEffectOnKing, royal prerogatives reaffirmed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalEffectOnKing Context triple: [Mise of Amiens, legalEffectOnKing, royal prerogatives reaffirmed]
-
A.
kingIsInviolable
Indicates that the king is protected from harm, violation, or infringement, often implying legal or moral immunity from certain actions.
-
B.
declaredKingWhileDavidAlive
Indicates that someone was proclaimed or assumed the role of king during a time when David was still alive.
-
C.
hasKing
Indicates that an entity possesses or is ruled by a king.
-
D.
hasKingAsSubject
Indicates that the subject entity in the relationship is a king.
-
E.
selectedAsKing
Indicates that an entity has been chosen or appointed to hold the position or role of king.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea62d6448190a7f5b785467824cf |
completed | April 7, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69d4dfbc546881908f312c66ee195f79 |
completed | April 7, 2026, 10:43 a.m. |
| PDg | Predicate description generation | batch_69d4e91de3088190ae89cbb12fb29db8 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:13 p.m.