Triple
T11330591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota Kluger |
E268331
|
entity |
| Predicate | offersHybridVariantIn |
P98538
|
FINISHED |
| Object | Australia (recent generation) |
—
|
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: Australia (recent generation) | Statement: [Toyota Kluger, offersHybridVariantIn, Australia (recent generation)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersHybridVariantIn Context triple: [Toyota Kluger, offersHybridVariantIn, Australia (recent generation)]
-
A.
hasCommercialVariant
Indicates that an entity has a related version that is produced, marketed, or sold commercially.
-
B.
offersFeature
Indicates that one entity provides or makes available a particular feature or capability to another entity.
-
C.
isOfferedBy
Indicates that a service, product, or opportunity is provided or made available by a particular entity.
-
D.
offersServiceIn
Indicates that a provider makes a particular service available within a specified location or jurisdiction.
-
E.
serviceVariantOf
Indicates that one service is a variant or alternative version of another, typically differing in configuration, features, or options while serving a similar core function.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9fd38308190a5458be1bfcc89ea |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:32 p.m.