Triple
T6087690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Decree of 24 March 1815 |
E135679
|
entity |
| Predicate | typeOfHonorRegulated |
P4123
|
FINISHED |
| Object | civil order of merit |
—
|
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: civil order of merit | Statement: [Royal Decree of 24 March 1815, typeOfHonorRegulated, civil order of merit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfHonorRegulated Context triple: [Royal Decree of 24 March 1815, typeOfHonorRegulated, civil order of merit]
-
A.
honourType
chosen
Indicates the specific category or classification of an honour or award associated with an entity.
-
B.
isCivilianHonourGrade
Indicates that one entity is classified as a specific grade or level within a system of civilian honours or awards in relation to another entity.
-
C.
honorLevel
Indicates the degree or status of respect, distinction, or recognition accorded to an entity relative to others.
-
D.
honoraryAwardsEligibleFor
Indicates that an entity qualifies to receive one or more honorary awards.
-
E.
honorsRoleAs
Indicates that one entity shows respect, recognition, or deference to another entity specifically in their official position or function.
- 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_69c0087bcc788190b20f093d3a6c60ec |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0578bf2508190859c2dbd4c10b316 |
completed | March 22, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c049f3b1ec8190bea67a7bec6442a5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:12 p.m.