Triple
T4805798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanleys of Alderley |
E106943
|
entity |
| Predicate | hasHereditaryTitleCreationDate |
P31263
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Stanleys of Alderley, hasHereditaryTitleCreationDate, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHereditaryTitleCreationDate Context triple: [Stanleys of Alderley, hasHereditaryTitleCreationDate, 19th century]
-
A.
nobleTitleCreationDate
chosen
Indicates the date on which a particular noble title was formally created or granted.
-
B.
dateGrantedHonorificTitle
Indicates the date on which an entity was formally awarded or granted an honorific title.
-
C.
hasTitleSince
Indicates that an entity has held a particular title continuously starting from a specified point in time.
-
D.
hasHereditaryChief
Indicates that an entity is led or governed by a chief whose position is inherited through family lineage.
-
E.
hasHeirApparentTitle
Indicates that an entity holds a title designating them as the officially recognized heir apparent to another entity’s position or rank.
- 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_69bd43f6a1e08190bf0a372bfc336ee5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1c43a48190a65e56b1624a2339 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:23 p.m.