Triple
T3320561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Beaconsfield |
E69784
|
entity |
| Predicate | honourContext |
P4129
|
FINISHED |
| Object | honour for political service |
—
|
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: honour for political service | Statement: [Earl of Beaconsfield, honourContext, honour for political service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honourContext Context triple: [Earl of Beaconsfield, honourContext, honour for political service]
-
A.
honourTypeContext
chosen
Indicates the specific situational or cultural context in which an honour or form of respect is expressed or applies.
-
B.
honour
Indicates showing respect, admiration, or recognition toward someone or something, often through actions, words, or ceremonial acknowledgment.
-
C.
honourType
Indicates the specific category or classification of an honour or award associated with an entity.
-
D.
honoredThrough
Indicates that one entity is recognized or commemorated by means of another entity, event, or action.
-
E.
honourStyle
Indicates a relationship where one entity follows, respects, or upholds the manner, customs, or stylistic approach associated with another.
- 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_69ad85a0bb048190a5458d2738012d61 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb13b85208190b13aba355d5dafcf |
completed | March 8, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69ada42a19348190a3862ce02451f4aa |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.