Triple
T11266270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lane’s End Farm |
E266693
|
entity |
| Predicate | breeds |
P41121
|
FINISHED |
| Object | Thoroughbred racehorses |
—
|
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 racehorses | Statement: [Lane’s End Farm, breeds, Thoroughbred racehorses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breeds Context triple: [Lane’s End Farm, breeds, Thoroughbred racehorses]
-
A.
breed
Indicates that an organism reproduces to generate offspring, typically with another organism of the same species.
-
B.
breedsIn
Indicates that an organism reproduces or carries out its breeding activities within a specified environment, habitat, or location.
-
C.
associatedAnimalBreed
chosen
Indicates that there is a relationship linking an entity to a specific breed of animal with which it is connected or identified.
-
D.
originBreeds
Indicates that one entity is the place or source from which another entity (typically a breed or type) originates or was developed.
-
E.
isHeritageBreed
Indicates that an animal breed belongs to a traditional, historically established lineage recognized for its cultural, genetic, or agricultural heritage.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e94e5e3c8190a31995d55d20d7ed |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d7879bc56c8190b2e8d2193f29de05 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.