Triple
T30415982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Her Grace |
E773756
|
entity |
| Predicate | addressFormRelative |
P4477
|
FINISHED |
| Object | Your Grace |
—
|
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: Your Grace | Statement: [Her Grace, addressFormRelative, Your Grace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressFormRelative Context triple: [Her Grace, addressFormRelative, Your Grace]
-
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.
addressMode
Indicates how data or resources are accessed or referenced within a system, such as the method or scheme used to locate them.
-
C.
addressLocal
Indicates that one entity serves as a local or nearby address or location reference for another entity.
-
D.
addressFormat
Indicates the standardized structure or pattern in which an address’s components are arranged and written.
-
E.
addressRepresents
Indicates that one address stands for, corresponds to, or serves as the official representation of another entity or location.
- 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 29, 2026, 8:05 p.m.