Triple
T5760449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comes de Fyf |
E127077
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical title designation |
C12813
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historical title designation Context triple: [Comes de Fyf, instanceOf, historical title designation]
-
A.
historical person designation
chosen
A historical person designation is a label or title used to identify and categorize an individual from the past based on their role, status, or significance in history.
-
B.
historic designation
A historic designation is an official recognition granted to a place, structure, or object for its significant historical, architectural, cultural, or archaeological value, often providing it with legal protections and conservation guidelines.
-
C.
system of hereditary titles
A system of hereditary titles is a structured hierarchy of ranks and honors that are legally or socially passed down through family lines, typically from one generation to the next.
-
D.
historical position
A historical position is a specific role, office, or status held by an individual within a past social, political, or cultural context, defined by its responsibilities, authority, and time period.
-
E.
historical military rank
A historical military rank is a formally defined level of authority and responsibility within past armed forces, reflecting the hierarchical structure, duties, and social status of military personnel in a specific historical context.
- F. None of above.
Provenance (1 batch)
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. |
Created at: March 22, 2026, 3:49 p.m.