Triple
T15231846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deputy Lieutenant |
E364021
|
entity |
| Predicate | mayActOnBehalfOf |
P4131
|
FINISHED |
| Object | Lord Lieutenant at events |
—
|
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: Lord Lieutenant at events | Statement: [Deputy Lieutenant, mayActOnBehalfOf, Lord Lieutenant at events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayActOnBehalfOf Context triple: [Deputy Lieutenant, mayActOnBehalfOf, Lord Lieutenant at events]
-
A.
actsOnBehalfOf
chosen
Indicates that one entity performs actions or makes decisions as a representative or proxy for another entity.
-
B.
appointedOnBehalfOf
Indicates that an appointment or designation is made by one party acting in representation of, or for the benefit of, another party.
-
C.
builtOnBehalfOf
Indicates that something was constructed or created by one party acting as a representative or agent for another party.
-
D.
presentedOnBehalfOf
Indicates that an action, statement, or presentation was made by one party while formally representing or acting for another party.
-
E.
mayActThrough
Indicates that an entity can exert influence, perform an action, or have an effect by means of another entity, mechanism, or intermediary.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0078e27408190bc13c0ca441f5594 |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:12 a.m.