Triple
T10041756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bandvagn 206 |
E205310
|
entity |
| Predicate | hasGroundPressure |
P91791
|
FINISHED |
| Object | very low |
—
|
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: very low | Statement: [Bandvagn 206, hasGroundPressure, very low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGroundPressure Context triple: [Bandvagn 206, hasGroundPressure, very low]
-
A.
usesGroundSystem
Indicates that one entity operates, relies on, or interacts with a particular ground-based system to perform its functions or services.
-
B.
surfacePressure
Indicates the pressure exerted by a fluid (such as air or water) on the surface of an object or body.
-
C.
hasPressureSphere
Indicates a relationship where an entity possesses or is associated with a defined region or volume characterized by a specific pressure condition.
-
D.
hasHumanPressure
Indicates that one entity exerts or experiences human-induced influence, stress, or impact in relation to another entity or environment.
-
E.
isGroundedIn
Indicates that something is based on, supported by, or justified through a particular source, foundation, or set of principles.
- 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcee48d8c8190af7c93b60f8ca7cb |
completed | April 2, 2026, 2:05 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:55 p.m.