Triple
T10085743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscount Formartine |
E215215
|
entity |
| Predicate | isUsedAsCourtesyTitle |
P81246
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Viscount Formartine, isUsedAsCourtesyTitle, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedAsCourtesyTitle Context triple: [Viscount Formartine, isUsedAsCourtesyTitle, yes]
-
A.
usedAsCourtesyTitleFor
chosen
Indicates that one entity serves as a courtesy title or honorific form of address applied to another entity.
-
B.
usedInFormalTitleOf
Indicates that something is employed as part of the official or formal title of an entity.
-
C.
isHonorific
Indicates that one entity functions as an honorific title or respectful form of address applied to another entity.
-
D.
hasPatronalTitle
Indicates that an entity holds or is associated with a specific patronal or honorific title, typically reflecting patronage, protection, or dedication.
-
E.
traditionalCourtesyTitleHeir
Indicates that one entity holds the customary or historically recognized courtesy title associated with being the heir 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_69ca83a1eed081908b2e9580f2ebeea7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd04609748190987a9364a387fa61 |
completed | April 2, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4b97870481908f7a89df10d58a9e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9 p.m.