Triple
T37214150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Ellenborough |
E922688
|
entity |
| Predicate | hasFirstHolderBirthYear |
P11702
|
FINISHED |
| Object | 1790 |
—
|
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: 1790 | Statement: [Earl of Ellenborough, hasFirstHolderBirthYear, 1790]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstHolderBirthYear Context triple: [Earl of Ellenborough, hasFirstHolderBirthYear, 1790]
-
A.
valueForBirthYears
Indicates a relationship where a specific value is associated with or derived from entities’ years of birth.
-
B.
namedAfterBirthYear
Indicates that one entity is named based on, or in reference to, the birth year of another entity.
-
C.
hasFirstHolderFamilyName
Indicates that an entity is associated with the family name (surname) of its first holder.
-
D.
notableBearerBirthYear
chosen
Indicates the year in which a notable bearer of the referenced name, title, or identifier was born.
-
E.
yearOfBirth
Indicates the specific calendar year in which an entity was born.
- 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_69f76ea6f5288190b8d9988f613811c0 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a004d0b46148190bcec4ea67acfe170 |
completed | May 10, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_6a004c92283081909f229c1720af155a |
completed | May 10, 2026, 9:14 a.m. |
Created at: May 3, 2026, 4:15 p.m.