Triple
T4416155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Field Marshal (British Army) |
E94978
|
entity |
| Predicate | honoraryAwardedTo |
P45356
|
FINISHED |
| Object | members of the British royal family |
—
|
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: members of the British royal family | Statement: [Field Marshal (British Army), honoraryAwardedTo, members of the British royal family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honoraryAwardedTo Context triple: [Field Marshal (British Army), honoraryAwardedTo, members of the British royal family]
-
A.
includesHonoraryAwardsFor
Indicates that one entity contains or lists honorary awards that have been granted to another entity.
-
B.
honoredPerson
Indicates that a person is the recipient of honor, recognition, or special distinction from another party or in a particular context.
-
C.
honoreeRole
Indicates the specific role, title, or capacity in which an individual is being honored in relation to an award, event, or recognition.
-
D.
yearHonored
Indicates the specific year in which an entity received an honor, award, or formal recognition.
-
E.
recipientOfAward
chosen
Indicates that an entity has received or been granted a particular award.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3551afb448190a2ce2000193808ac |
completed | March 13, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69b34f5d0c54819085c08533bb58030a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:29 p.m.