Triple
T20992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Merit |
E416
|
entity |
| Predicate | appointmentsMadeBy |
P257
|
FINISHED |
| Object | sovereign personally |
—
|
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: sovereign personally | Statement: [Order of Merit, appointmentsMadeBy, sovereign personally]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointmentsMadeBy Context triple: [Order of Merit, appointmentsMadeBy, sovereign personally]
-
A.
appointedBy
chosen
Indicates that one entity has been formally selected or assigned to a position, role, or office by another entity.
-
B.
meetsAs
Indicates that two entities encounter or come together at the same place and time, typically in a planned or recognized interaction.
-
C.
createdBy
Indicates that something was brought into existence, produced, or authored through the actions or efforts of a specific agent or entity.
-
D.
composedBy
Indicates that one entity is the creator or author of a musical or artistic work associated with another entity.
-
E.
staffIncluded
Indicates that staff members are included or provided as part of the associated entity, service, or arrangement.
- 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_69a240778d288190815c0052ebbbcc91 |
completed | Feb. 28, 2026, 1:10 a.m. |
| NER | Named-entity recognition | batch_69a246f7bd30819085f751c41f6f029e |
completed | Feb. 28, 2026, 1:37 a.m. |
| PD | Predicate disambiguation | batch_69a246526f5881909bc2a46e978bd082 |
completed | Feb. 28, 2026, 1:35 a.m. |
Created at: Feb. 28, 2026, 1:14 a.m.