Triple
T1579834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Lieutenant of Lancashire |
E33735
|
entity |
| Predicate | honoursSystemRole |
P32837
|
FINISHED |
| Object | advises on local honours nominations |
—
|
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: advises on local honours nominations | Statement: [Lord Lieutenant of Lancashire, honoursSystemRole, advises on local honours nominations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honoursSystemRole Context triple: [Lord Lieutenant of Lancashire, honoursSystemRole, advises on local honours nominations]
-
A.
honoursSystem
Indicates that an entity follows or complies with a particular system of rules, standards, or principles.
-
B.
belongsToHonoursSystem
Indicates that something is a component or member of a specific honours or awards system.
-
C.
honourType
Indicates the specific category or classification of an honour or award associated with an entity.
-
D.
honourSystem
Indicates a relationship where compliance, access, or behavior is governed by trust in individuals to act honestly without direct enforcement or verification.
-
E.
honorificRank
Indicates that one entity holds a formal title or honorific status in relation to another entity.
- F. None of above. chosen
Provenance (4 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_69a885f27a4c8190a4622252cdf54c00 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abacfb1144819080c5687175aba1e1 |
completed | March 7, 2026, 4:43 a.m. |
| PD | Predicate disambiguation | batch_69aa61b0f5bc8190b1dc272990a59c13 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69abacf991148190b20521c063f93bfd |
completed | March 7, 2026, 4:43 a.m. |
Created at: March 4, 2026, 7:27 p.m.