Triple
T3523355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eclipse Stakes |
E74477
|
entity |
| Predicate | typicalWeightCondition |
P34734
|
FINISHED |
| Object | weight-for-age with penalties |
—
|
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: weight-for-age with penalties | Statement: [Eclipse Stakes, typicalWeightCondition, weight-for-age with penalties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWeightCondition Context triple: [Eclipse Stakes, typicalWeightCondition, weight-for-age with penalties]
-
A.
weightStandardInfluencedBy
chosen
Indicates that a weight standard is affected, shaped, or determined by another factor, standard, or influence.
-
B.
typicalBodyType
Indicates that one entity is the usual or characteristic body type associated with another entity.
-
C.
averageWeight
Indicates the typical or mean weight value associated with an entity or group of entities.
-
D.
weightRangeDescription
Indicates the textual description that specifies the range within which an entity’s weight falls.
-
E.
approximateWeightInPounds
Indicates the estimated weight of an entity expressed in pounds, rather than an exact measured value.
- 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc4f16b8819094ad2755670ddc7b |
completed | March 8, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69adae121a048190b03825a001d21f49 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.