Triple
T16806454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regal Sportback |
E408493
|
entity |
| Predicate | hasCargoAccess |
P124919
|
FINISHED |
| Object | top-hinged rear hatch |
—
|
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: top-hinged rear hatch | Statement: [Regal Sportback, hasCargoAccess, top-hinged rear hatch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCargoAccess Context triple: [Regal Sportback, hasCargoAccess, top-hinged rear hatch]
-
A.
hasCargoDoorVariant
Indicates that one entity is a specific cargo-door-equipped version or configuration variant of another entity.
-
B.
cargoAccess
Indicates that an entity has permission or capability to access, enter, or interact with a cargo area or cargo-related contents.
-
C.
hasTrunk
Indicates that one entity possesses or is equipped with a trunk as a physical feature or component.
-
D.
supportsCargoType
Indicates that one entity is capable of handling, transporting, or accommodating a specified type of cargo.
-
E.
hasPassengerArea
Indicates that an object or vehicle includes a designated area intended for carrying passengers.
- F. None of above. chosen
Provenance (4 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2cd1e8c8190a7a05ba255f711c7 |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e34fb7c8c8819086975b7955b7d8ef |
completed | April 18, 2026, 9:32 a.m. |
Created at: April 10, 2026, 5:22 a.m.