Triple
T16261539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Hunt of Llanfair Waterdine |
E394765
|
entity |
| Predicate | honoursContext |
P4129
|
FINISHED |
| Object | British honours system |
—
|
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: British honours system | Statement: [Baron Hunt of Llanfair Waterdine, honoursContext, British honours system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honoursContext Context triple: [Baron Hunt of Llanfair Waterdine, honoursContext, British honours system]
-
A.
honourTypeContext
chosen
Indicates the specific situational or cultural context in which an honour or form of respect is expressed or applies.
-
B.
honoursPeriod
Indicates the time span during which an honour, award, or recognition is valid, held, or in effect for an entity.
-
C.
honoursSystem
Indicates that an entity follows or complies with a particular system of rules, standards, or principles.
-
D.
honourOf
Indicates that one entity is the source, bearer, or cause of another entity’s honor, prestige, or distinguished recognition.
-
E.
honoursFunction
Indicates that one entity formally recognizes, celebrates, or pays tribute to another through a designated function, event, or ceremony.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c4a0b08190af3574f087205afc |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.