Triple
T18110644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Oaks estate |
E433463
|
entity |
| Predicate | raceNamedAfterIsClass |
P117813
|
FINISHED |
| Object | British Classic race |
—
|
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: British Classic race | Statement: [The Oaks estate, raceNamedAfterIsClass, British Classic race]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceNamedAfterIsClass Context triple: [The Oaks estate, raceNamedAfterIsClass, British Classic race]
-
A.
hasRaceNamedAfter
chosen
Indicates that an entity has a race or competition that is named in honor of, or after, another entity.
-
B.
raceName
Indicates the specific race or competition designation associated with an entity or event.
-
C.
notableRaceClass
Indicates that there exists a notable race or competition of a particular class or category associated with the subject.
-
D.
hasRaceClass
Indicates that an entity participates in or is associated with a particular race classification or category.
-
E.
namedAccordingTo
Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd2038081909515fb6d17495cbf |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.