Triple
T29647766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McLaren GT |
E756049
|
entity |
| Predicate | luggageCapacity |
P116491
|
FINISHED |
| Object | front and rear luggage compartments |
—
|
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: front and rear luggage compartments | Statement: [McLaren GT, luggageCapacity, front and rear luggage compartments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: luggageCapacity Context triple: [McLaren GT, luggageCapacity, front and rear luggage compartments]
-
A.
hasOnboardLuggageSpace
chosen
Indicates that an entity provides or includes dedicated space for carrying luggage on board.
-
B.
hasLuggage
Indicates that an entity is carrying, possessing, or associated with one or more pieces of luggage.
-
C.
allowsLuggage
Indicates that one entity permits another entity to bring or carry luggage in a given context.
-
D.
externalPayloadCapacity
Indicates the maximum weight of payload that can be carried externally (outside the main body or cargo area) by an entity.
-
E.
slingLoadCapacity
Indicates the maximum weight or load that can be safely carried or supported using a sling.
- 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.