Triple
T25404084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Deakins |
E636503
|
entity |
| Predicate | formOfAddress |
P4477
|
FINISHED |
| Object | Lady Deakins |
—
|
NE NERFINISHED |
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: Lady Deakins | Statement: [Lady Deakins, formOfAddress, Lady Deakins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formOfAddress Context triple: [Lady Deakins, formOfAddress, Lady Deakins]
-
A.
addressFormFor
chosen
Indicates the form of address or mode of speaking that one entity should use when referring to or speaking to another entity.
-
B.
addressFormat
Indicates the standardized structure or pattern in which an address’s components are arranged and written.
-
C.
addressType
Indicates the specific kind or category of address associated with an entity (e.g., home, work, billing, or shipping).
-
D.
postalAddressFor
Indicates that one entity serves as the postal address associated with, or used for sending mail to, another entity.
-
E.
addressingType
Indicates the manner or form in which one entity addresses or refers to another (e.g., formally, informally, by title, or by name).
- 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_69e75db361d881908d8701c856da6413 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f584fcac20819093a4919df2ef23b6 |
completed | May 2, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:52 p.m.