Triple
T29259876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Her Honour |
E741811
|
entity |
| Predicate | addressPosition |
P83823
|
FINISHED |
| Object | placed before the person’s name |
—
|
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: placed before the person’s name | Statement: [Her Honour, addressPosition, placed before the person’s name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressPosition Context triple: [Her Honour, addressPosition, placed before the person’s name]
-
A.
addressesPosition
Indicates that one entity communicates with, responds to, or deals with the role, status, or job position held by another entity.
-
B.
addresseePosition
chosen
Indicates the spatial or positional relationship of the addressee relative to a reference point or speaker.
-
C.
address
Indicates that one entity directs spoken or written communication specifically to another entity.
-
D.
addressArea
Indicates the geographic area or region that an address is located in or associated with.
-
E.
addressType
Indicates the specific kind or category of address associated with an entity (e.g., home, work, billing, or shipping).
- 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 12:40 p.m.