Triple
T25796258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Clifden |
E649690
|
entity |
| Predicate | leadingSireYear |
P117807
|
FINISHED |
| Object | 1876 |
—
|
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: 1876 | Statement: [Lord Clifden, leadingSireYear, 1876]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadingSireYear Context triple: [Lord Clifden, leadingSireYear, 1876]
-
A.
leadingSireTitle
Indicates that an entity holds the distinction of being the most successful sire (in terms of progeny performance) within a defined period or category.
-
B.
leadingSireInGreatBritain
chosen
Indicates that a male horse was the most successful sire in Great Britain for a given period, typically based on the racing performance or earnings of its offspring.
-
C.
mostSuccessfulHorseYears
Indicates the years during which a particular horse achieved its highest level of success or best performance relative to other years.
-
D.
raceYear
Indicates the specific calendar year in which a particular race event takes place.
-
E.
leaderSince
Indicates that an entity has held a leadership role over another entity starting from a specified point in time.
- 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 6:30 a.m.