Triple
T38402655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Night of Thunder |
E900941
|
entity |
| Predicate | hasThoroughbredFamily |
P75522
|
FINISHED |
| Object | Thoroughbred family 1-n |
—
|
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: Thoroughbred family 1-n | Statement: [Night of Thunder, hasThoroughbredFamily, Thoroughbred family 1-n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThoroughbredFamily Context triple: [Night of Thunder, hasThoroughbredFamily, Thoroughbred family 1-n]
-
A.
thoroughbredFamily
chosen
Indicates that one entity belongs to, or is classified within, a specific Thoroughbred horse family lineage associated with the other entity.
-
B.
ownedRacehorse
Indicates that one entity possessed legal ownership of a particular racehorse.
-
C.
usesHorsesBredBy
Indicates that one entity makes use of horses that have been bred by another entity.
-
D.
horseBreed
Indicates that one entity is a specific breed of the horse represented by the other entity.
-
E.
hasRacehorseCharacter
Indicates that one entity possesses the traits, qualities, or behavioral characteristics associated with a racehorse in relation to another entity or context.
- 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.