Triple
T5760468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comes de Fyf |
E127077
|
entity |
| Predicate | hasTitleCategory |
P18941
|
FINISHED |
| Object | hereditary peerage title |
—
|
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: hereditary peerage title | Statement: [Comes de Fyf, hasTitleCategory, hereditary peerage title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleCategory Context triple: [Comes de Fyf, hasTitleCategory, hereditary peerage title]
-
A.
hasTitleType
chosen
Indicates that an entity holds a specific kind or category of title (such as job title, honorific, or formal designation).
-
B.
hasTitleSubject
Indicates that an entity has a specific subject or topic as the focus of its title.
-
C.
containsTitle
Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
-
D.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
-
E.
hasTitleSince
Indicates that an entity has held a particular title continuously starting from a specified point in time.
- 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_69c00833a3fc81908f4bc29ed011b7a6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02938972c8190992149ea943f87bf |
completed | March 22, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69c021cc68648190bb86d049ebe80f12 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:49 p.m.