Triple
T10849774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Brown Jug |
E256113
|
entity |
| Predicate | eligibleHorses |
P96062
|
FINISHED |
| Object | three-year-old Standardbred 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: three-year-old Standardbred horses | Statement: [Little Brown Jug, eligibleHorses, three-year-old Standardbred horses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibleHorses Context triple: [Little Brown Jug, eligibleHorses, three-year-old Standardbred horses]
-
A.
horseBreed
Indicates that one entity is a specific breed of the horse represented by the other entity.
-
B.
featuresHorse
Indicates that something includes, presents, or prominently involves a horse as a central element or subject.
-
C.
hasNotableHorse
Indicates that an entity is associated with a horse that is considered notable or distinguished in some recognized way.
-
D.
horseColor
Indicates the relationship that specifies what color a given horse is.
-
E.
hasNotableJockey
Indicates that an entity (typically a racehorse) is or was ridden by a jockey who is considered notable or distinguished.
- F. None of above. chosen
Provenance (4 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75115e4a88190b77be46b63db0c84 |
completed | April 9, 2026, 7:11 a.m. |
| PD | Predicate disambiguation | batch_69d70d2b51448190bae748ed6c23edde |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101c96708190808fef73199e8482 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:20 p.m.