Triple
T30565398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grafton family |
E777958
|
entity |
| Predicate | notableTitleCreationYear |
P87128
|
FINISHED |
| Object | 1675 |
—
|
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: 1675 | Statement: [Grafton family, notableTitleCreationYear, 1675]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTitleCreationYear Context triple: [Grafton family, notableTitleCreationYear, 1675]
-
A.
notableTitleReleaseYear
Indicates the year in which a notable work or title associated with an entity was released.
-
B.
notableProductionYear
Indicates the year in which an entity produced something considered notable or significant.
-
C.
EuroTitleYear
Indicates the year in which an entity received or held a specific European title or championship.
-
D.
notableTitleType
Indicates that a title associated with an entity is of a type considered notable or especially significant.
-
E.
yearTitleCreated
chosen
Indicates the year in which the referenced title (such as a work, document, or creative piece) was originally created.
- 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_69f2249ed41c8190b175170ecfd6e1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:21 p.m.