Triple
T32787049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bv 206D |
E838525
|
entity |
| Predicate | hasCargoSpaceLocation |
P148162
|
FINISHED |
| Object | rear unit |
—
|
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 unit | Statement: [Bv 206D, hasCargoSpaceLocation, rear unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCargoSpaceLocation Context triple: [Bv 206D, hasCargoSpaceLocation, rear unit]
-
A.
cargoSpace
Indicates that one entity provides storage capacity or room for carrying goods, equipment, or other items for another entity.
-
B.
hasCargoAccess
Indicates that an entity has the ability or permission to access a designated cargo area or its contents.
-
C.
hasCargoHold
chosen
Indicates that something possesses a dedicated space or compartment for storing or transporting cargo.
-
D.
hasPassengerArea
Indicates that an object or vehicle includes a designated area intended for carrying passengers.
-
E.
hasOnboardLuggageSpace
Indicates that an entity provides or includes dedicated space for carrying luggage on board.
- 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
Created at: May 1, 2026, 1:14 a.m.