Triple
T16321845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Brown Jug |
E396312
|
entity |
| Predicate | JugetteEligibility |
P112795
|
FINISHED |
| Object | 3-year-old pacing fillies |
—
|
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: 3-year-old pacing fillies | Statement: [Little Brown Jug, JugetteEligibility, 3-year-old pacing fillies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: JugetteEligibility Context triple: [Little Brown Jug, JugetteEligibility, 3-year-old pacing fillies]
-
A.
isCollectibleFigure
Indicates that an entity is a figure or model intended primarily for collection rather than ordinary use or play.
-
B.
hasFictionalProduct
Indicates a relationship where one entity features, offers, or includes a product that exists only in fiction or an imagined context.
-
C.
eligibleProducts
chosen
Indicates that certain products meet the required criteria or conditions to qualify for a specified offer, action, or status.
-
D.
toyType
Indicates the specific category or kind of toy that an item belongs to.
-
E.
isSuitableFor
Indicates that one entity is appropriate, fitting, or well-matched for use, application, or association with another entity.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b706108190b43a05b784633050 |
completed | April 17, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.