Triple
T29647767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McLaren GT |
E756049
|
entity |
| Predicate | rearLuggageCapacity |
P116491
|
FINISHED |
| Object | sized to carry golf bags or skis |
—
|
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: sized to carry golf bags or skis | Statement: [McLaren GT, rearLuggageCapacity, sized to carry golf bags or skis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rearLuggageCapacity Context triple: [McLaren GT, rearLuggageCapacity, sized to carry golf bags or skis]
-
A.
cargoSpace
Indicates that one entity provides storage capacity or room for carrying goods, equipment, or other items for another entity.
-
B.
hasOnboardLuggageSpace
chosen
Indicates that an entity provides or includes dedicated space for carrying luggage on board.
-
C.
externalPayloadCapacity
Indicates the maximum weight of payload that can be carried externally (outside the main body or cargo area) by an entity.
-
D.
cargoCapacityFeature
Indicates that an entity has a feature specifying how much cargo it can carry or accommodate.
-
E.
vehicleDeckCapacity
Indicates the maximum number or volume of vehicles that a deck is designed to 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f66ed3d37c81909b3e973fb9dd70cc |
completed | May 2, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:50 p.m.