Triple
T1694335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jane Elizabeth Ebsworth Oriel |
E36621
|
entity |
| Predicate | spouseHonorificTitle |
P17687
|
FINISHED |
| Object | Sir |
—
|
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: Sir | Statement: [Jane Elizabeth Ebsworth Oriel, spouseHonorificTitle, Sir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseHonorificTitle Context triple: [Jane Elizabeth Ebsworth Oriel, spouseHonorificTitle, Sir]
-
A.
hasSpouseTitle
chosen
Indicates that a person’s spouse holds a particular title or honorific designation.
-
B.
spouseOfHonouree
Indicates that one person is the spouse (married partner) of the honouree.
-
C.
honorificTitle
Indicates that one entity serves as a formal honorific or respectful title used to address or refer to another entity.
-
D.
honorificPrefix
Indicates the formal title or respectful prefix (e.g., "Dr.", "Mr.", "Prof.") used before a person's name to denote status, role, or honor.
-
E.
spouseOffice
Indicates that one entity holds an office or position that is associated with, or held by, the spouse of another entity.
- 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_69a886163dec8190859c514232a37a05 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf169da888190b3aa334752f1952b |
completed | March 6, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69aa61b8ce348190b46154af0b041ff0 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.