Triple
T38475833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bergepanther |
E915545
|
entity |
| Predicate | winchCapacity |
P84310
|
FINISHED |
| Object | up to 40 tonnes |
—
|
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: up to 40 tonnes | Statement: [Bergepanther, winchCapacity, up to 40 tonnes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winchCapacity Context triple: [Bergepanther, winchCapacity, up to 40 tonnes]
-
A.
hasWinchCapacity
chosen
Indicates that an entity is equipped with a winch capable of exerting or handling a specified load or pulling capacity.
-
B.
slingLoadCapacity
Indicates the maximum weight or load that can be safely carried or supported using a sling.
-
C.
hasWinch
Indicates that one entity is equipped with or possesses a winch mechanism.
-
D.
hasCraneCapacity
Indicates that an entity possesses a crane with a specified lifting capacity or load-handling capability.
-
E.
cargoCapacityFeature
Indicates that an entity has a feature specifying how much cargo it can carry or accommodate.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.