Triple
T3504005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palo Alto Stock Farm |
E74031
|
entity |
| Predicate | breedingProgramType |
P32573
|
FINISHED |
| Object | Standardbred trotting horses |
—
|
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: Standardbred trotting horses | Statement: [Palo Alto Stock Farm, breedingProgramType, Standardbred trotting horses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breedingProgramType Context triple: [Palo Alto Stock Farm, breedingProgramType, Standardbred trotting horses]
-
A.
breedingMethod
Indicates the technique or process by which organisms are bred or reproduced.
-
B.
breedingGoal
Indicates that one entity is the intended objective or target outcome of a breeding process involving another entity.
-
C.
breedingUse
chosen
Indicates that one entity is used for breeding or reproductive purposes with respect to another entity.
-
D.
hasBreedingCode
Indicates that an entity is associated with a specific code representing its breeding status, behavior, or category.
-
E.
breeder
Indicates that an entity is responsible for producing, raising, or propagating another entity, typically through controlled reproduction.
- 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbf22b1c8190956141d8fb924210 |
completed | March 8, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69adae0cd8b0819099da300af09880da |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.