Triple
T22661168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lecomte Stakes |
E559664
|
entity |
| Predicate | weightCondition |
P149113
|
FINISHED |
| Object | assigned 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 with allowances | Statement: [Lecomte Stakes, weightCondition, assigned with allowances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weightCondition Context triple: [Lecomte Stakes, weightCondition, assigned with allowances]
-
A.
weightIssue
Indicates that there is a problem, concern, or abnormal condition related to the weight of an entity.
-
B.
weight
Indicates a relationship where a numerical value quantifies how heavy an entity is, often used to measure or compare mass or load.
-
C.
weightSize
Indicates a relationship between an entity’s weight and its physical size, typically expressing how one varies or is characterized in terms of the other.
-
D.
weightRangeDescription
Indicates the textual description that specifies the range within which an entity’s weight falls.
-
E.
weightSupport
Indicates that one entity bears or carries the physical weight of another, providing structural or mechanical support.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1765fe7d081908087778c54c1e612 |
completed | April 29, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:07 p.m.