Triple
T1165822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchess of York |
E24596
|
entity |
| Predicate | firstCreationCentury |
P6026
|
FINISHED |
| Object | 14th century |
—
|
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: 14th century | Statement: [Duchess of York, firstCreationCentury, 14th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCreationCentury Context triple: [Duchess of York, firstCreationCentury, 14th century]
-
A.
originalCentury
Indicates the century in which something was originally created, produced, or came into existence.
-
B.
introducedInCentury
chosen
Indicates the century during which something (such as an idea, technology, practice, or entity) was first introduced or came into use.
-
C.
century
Indicates that an entity is associated with, occurs in, or belongs to a particular 100-year time period.
-
D.
foundedInCentury
Indicates that an entity was established or came into existence during a specified century.
-
E.
discoveredInCentury
Indicates that an entity was discovered during a specific century.
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bccc62a88190882d8801908015a4 |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb548c1481909092626c572d8782 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.