Triple
T6558721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl Roberts |
E152518
|
entity |
| Predicate | honoursFor |
P2354
|
FINISHED |
| Object | distinguished military leader |
—
|
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: distinguished military leader | Statement: [Earl Roberts, honoursFor, distinguished military leader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honoursFor Context triple: [Earl Roberts, honoursFor, distinguished military leader]
-
A.
honourOf
Indicates that one entity is the source, bearer, or cause of another entity’s honor, prestige, or distinguished recognition.
-
B.
honoursSystem
Indicates that an entity follows or complies with a particular system of rules, standards, or principles.
-
C.
honourType
Indicates the specific category or classification of an honour or award associated with an entity.
-
D.
honors
chosen
Indicates that one entity shows respect, recognition, or esteem toward another entity, often in a formal or ceremonial way.
-
E.
nameHonors
Indicates that a name is given to honor, commemorate, or pay tribute to a particular entity.
- 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_69c688058d6881908c19b309cc55dbfa |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c1b15d3481908ae66e3d7564b352 |
completed | March 27, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c6acf6d4148190914b19e9affd8c76 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:52 p.m.