Triple
T13503077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaguar I-Pace |
E320940
|
entity |
| Predicate | cargoSpaceRearSeatsUp_l |
P46451
|
FINISHED |
| Object | around 656 |
—
|
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: around 656 | Statement: [Jaguar I-Pace, cargoSpaceRearSeatsUp_l, around 656]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoSpaceRearSeatsUp_l Context triple: [Jaguar I-Pace, cargoSpaceRearSeatsUp_l, around 656]
-
A.
cargoSpace
Indicates that one entity provides storage capacity or room for carrying goods, equipment, or other items for another entity.
-
B.
hasRetractableSeating
Indicates that an entity is equipped with seating that can be folded away, collapsed, or otherwise retracted when not in use.
-
C.
hasPassengerArea
Indicates that an object or vehicle includes a designated area intended for carrying passengers.
-
D.
cargoCapacityFeature
chosen
Indicates that an entity has a feature specifying how much cargo it can carry or accommodate.
-
E.
seatRecline
Indicates that one entity adjusts or is capable of adjusting the backward tilt or reclining position of a seat relative to another entity or context.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf810e248190a060481004503f96 |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.