Triple
T16515302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopeful Stakes |
E401166
|
entity |
| Predicate | hasWeightCondition |
P70576
|
FINISHED |
| Object | assigned weight with allowances |
—
|
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: assigned weight with allowances | Statement: [Hopeful Stakes, hasWeightCondition, assigned weight with allowances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWeightCondition Context triple: [Hopeful Stakes, hasWeightCondition, assigned weight with allowances]
-
A.
hasMinimumWeight
Indicates that an entity’s weight meets or exceeds a specified minimum threshold.
-
B.
requiresWeighIn
Indicates that one entity must provide an opinion, decision, or input before another entity’s action or process can proceed.
-
C.
isHeavierThan
Indicates that one entity has greater weight or mass than another entity.
-
D.
وزن
chosen
Indicates a relationship where one entity has, measures, or is characterized by a certain weight or mass.
-
E.
weightIssue
Indicates that there is a problem, concern, or abnormal condition related to the weight of an 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e7bbfa481909037148cdb4d8996 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.