Triple
T32750280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volvo A30D 6x6 articulated hauler |
E837475
|
entity |
| Predicate | loadHandling |
P25802
|
FINISHED |
| Object | rear tipping dump body |
—
|
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: rear tipping dump body | Statement: [Volvo A30D 6x6 articulated hauler, loadHandling, rear tipping dump body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loadHandling Context triple: [Volvo A30D 6x6 articulated hauler, loadHandling, rear tipping dump body]
-
A.
loader
Indicates a relationship where an entity is responsible for loading or placing items, data, or resources into another system, container, or context.
-
B.
loadingMechanism
chosen
Indicates the method or system by which something is loaded into or onto another object or structure.
-
C.
loadedWith
Indicates that one entity is carrying, filled with, or heavily supplied with another entity.
-
D.
loaderPosition
Indicates the spatial location or placement of a loader relative to a reference point or object.
-
E.
loadBearingFor
Indicates that one entity structurally supports and carries the weight or load of another entity.
- 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_69f34937f97c8190b7f84bea045df3ae |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:12 a.m.