Triple
T24378017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMI |
E614531
|
entity |
| Predicate | componentCapping |
P60454
|
FINISHED |
| Object | maximum weight per constituent applies |
—
|
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: maximum weight per constituent applies | Statement: [SMI, componentCapping, maximum weight per constituent applies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentCapping Context triple: [SMI, componentCapping, maximum weight per constituent applies]
-
A.
capped
chosen
Indicates that one entity has placed a limit or maximum boundary on another entity’s quantity, value, or extent.
-
B.
mayBeCappedBy
Indicates that one entity can optionally serve as a covering or cap for another entity.
-
C.
capacityCategory
Indicates the classification of something based on the amount or volume it can hold, handle, or accommodate.
-
D.
unitCapacity
Indicates the maximum quantity or load that a single unit is designed or allowed to hold, process, or accommodate.
-
E.
maximumCapacity
Indicates the greatest allowable or designed amount of something that an entity can hold, contain, or handle.
- 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293d96e7c8190b2f33a8fd12c32c6 |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:02 a.m.