Triple
T10042066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bergepanzer 2 |
E205318
|
entity |
| Predicate | craneLiftingCapacity |
P68727
|
FINISHED |
| Object | about 20 tonnes (approximate) |
—
|
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: about 20 tonnes (approximate) | Statement: [Bergepanzer 2, craneLiftingCapacity, about 20 tonnes (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: craneLiftingCapacity Context triple: [Bergepanzer 2, craneLiftingCapacity, about 20 tonnes (approximate)]
-
A.
hasCraneCapacity
chosen
Indicates that an entity possesses a crane with a specified lifting capacity or load-handling capability.
-
B.
hasWinchCapacity
Indicates that an entity is equipped with a winch capable of exerting or handling a specified load or pulling capacity.
-
C.
leoPayloadCapacity
Indicates the maximum payload mass or capacity that can be delivered to Low Earth Orbit (LEO) in the context of a launch vehicle or space mission.
-
D.
designedCargoCapacity
Indicates the maximum amount of cargo an object (such as a vehicle or container) was originally engineered or specified to carry.
-
E.
hasCrane
Indicates that an entity possesses, includes, or is equipped with a crane.
- 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_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. |
Created at: March 30, 2026, 8:55 p.m.