Triple
T9941993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marquess of Brackley |
E194104
|
entity |
| Predicate | notableBearerEra |
P84738
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Marquess of Brackley, notableBearerEra, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBearerEra Context triple: [Marquess of Brackley, notableBearerEra, 18th century]
-
A.
notableEra
Indicates the historical period or era for which an entity is especially recognized or significant.
-
B.
notableEraStart
Indicates the point in time when a notable or historically significant era associated with an entity begins.
-
C.
notableEraNickname
Indicates the informal or popular nickname by which a particular historical era or period is commonly known.
-
D.
hasNotableBearerCentury
chosen
Indicates that an entity has at least one notable bearer whose period of notability falls within the specified century.
-
E.
timePeriodOfNotableBearer
Indicates the span of time during which a notable bearer is recognized as having held, embodied, or been associated with the subject.
- 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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb610905c81909d669265c92021a5 |
completed | April 2, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:44 p.m.