Triple
T13426116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rally1 |
E313485
|
entity |
| Predicate | hasMinimumWeight |
P109859
|
FINISHED |
| Object | 1260 kg |
—
|
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: 1260 kg | Statement: [Rally1, hasMinimumWeight, 1260 kg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMinimumWeight Context triple: [Rally1, hasMinimumWeight, 1260 kg]
-
A.
hasMinimum
Indicates that an entity possesses at least a specified lower bound or smallest allowable value, quantity, or level in relation to another entity or constraint.
-
B.
hasMinimumSize
Indicates that an entity meets or exceeds a specified minimum size threshold.
-
C.
hasMinimumValue
Indicates that an entity possesses a value that is the lowest permissible or observed within a specified set, range, or context.
-
D.
hasMinimumLoadAmount
Indicates that there is a specified lowest allowable or required amount of load that must be met or exceeded.
-
E.
earlierMinimumWeight
Indicates that one entity reached or had the minimum weight value earlier in time than the other entity.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed066408190a416880affd8416e |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:40 p.m.