Triple
T5335450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M35 series 2½-ton 6x6 cargo truck |
E123814
|
entity |
| Predicate | payloadClass |
P32439
|
FINISHED |
| Object | 2½-ton |
—
|
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: 2½-ton | Statement: [M35 series 2½-ton 6x6 cargo truck, payloadClass, 2½-ton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payloadClass Context triple: [M35 series 2½-ton 6x6 cargo truck, payloadClass, 2½-ton]
-
A.
payloadType
Indicates the kind or category of payload associated with or carried by an entity or action.
-
B.
payloadCustomer
Indicates that a customer is associated with or carried as the payload within a given data structure, message, or transaction.
-
C.
payloadSpecialist
Indicates that an entity serves in the role of a payload specialist, responsible for managing or operating specific payloads or experiments in a mission or operation.
-
D.
supportedClass
chosen
Indicates that one entity is a class or type that is recognized, handled, or operable within the capabilities or context provided by another entity.
-
E.
positionClass
Indicates the classification or category assigned to an entity based on its role, rank, or position within a defined structure or system.
- 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_69bd464b07f8819095aa76577c9829e4 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85af799081909ee60bfbb65149ee |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2 p.m.