Triple
T14716143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Braddon |
E345683
|
entity |
| Predicate | hasNamesakeHonorific |
P31431
|
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: [Division of Braddon, hasNamesakeHonorific, Sir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamesakeHonorific Context triple: [Division of Braddon, hasNamesakeHonorific, Sir]
-
A.
hasHonorificNamesake
chosen
Indicates that an entity is named in honor of another entity, serving as a namesake that recognizes or commemorates the other.
-
B.
alsoHonoredAs
Indicates that an entity is additionally recognized or celebrated under another title, role, or form of honor beyond its primary designation.
-
C.
honorificNickname
Indicates that one entity is referred to by a respectful or honorific nickname by another entity or in a given context.
-
D.
hasHonorificName
Indicates that an entity is referred to by a formal or respectful title or name used as an honorific.
-
E.
honorificEponym
Indicates that one entity serves as an honorific namesake for another, typically recognizing or commemorating the person or entity in whose honor something is named.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb98688f48190b2b19ce7aa06a6db |
completed | April 14, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69de657e174481909da0437556334a04 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.