Triple
T13682934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-11 parachute |
E328045
|
entity |
| Predicate | intendedUserWeightClass |
P111155
|
FINISHED |
| Object | fully equipped combat soldier |
—
|
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: fully equipped combat soldier | Statement: [T-11 parachute, intendedUserWeightClass, fully equipped combat soldier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedUserWeightClass Context triple: [T-11 parachute, intendedUserWeightClass, fully equipped combat soldier]
-
A.
weightClass
Indicates the categorical grouping of an entity based on its weight range or mass classification.
-
B.
allowsWeightClasses
Indicates that one entity permits or supports the use of defined weight categories for another entity or within a given context.
-
C.
weightClassAlternativeName
Indicates that one weight class is referred to by an alternative name or label.
-
D.
weightClassBelow
Indicates that one entity belongs to a lower (lighter) weight class than another entity.
-
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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc66e75188190a9e82fdc5eb26513 |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:53 p.m.