Triple
T30087735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International HV Series |
E764642
|
entity |
| Predicate | typicalBodyApplications |
P125013
|
FINISHED |
| Object | dump truck |
—
|
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: dump truck | Statement: [International HV Series, typicalBodyApplications, dump truck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBodyApplications Context triple: [International HV Series, typicalBodyApplications, dump truck]
-
A.
hasTypicalBody
Indicates that an entity possesses the standard or characteristic physical form commonly associated with its kind or category.
-
B.
typicalBodyPart
Indicates that one entity is a body part that is characteristically or normally associated with another entity.
-
C.
appliesToBodyType
chosen
Indicates that something (such as a rule, feature, or specification) is relevant or applicable to a particular body type.
-
D.
appliedPrimarilyTo
Indicates that something is used mainly or chiefly in relation to a particular target, context, or purpose, rather than being used broadly or equally elsewhere.
-
E.
appliesPrimarilyTo
Indicates that a property, rule, or characteristic is mainly relevant or intended for a particular entity or group, more than for others.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a035ac41d088190b7e76b93c1410090 |
completed | May 12, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_6a035a4f290c8190a0101295a38ae8b8 |
completed | May 12, 2026, 4:50 p.m. |
Created at: April 29, 2026, 7:04 p.m.