Triple
T23350720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Park Ward |
E591998
|
entity |
| Predicate | vehicleTypeSpecializedIn |
P145772
|
FINISHED |
| Object | luxury saloons |
—
|
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: luxury saloons | Statement: [Park Ward, vehicleTypeSpecializedIn, luxury saloons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleTypeSpecializedIn Context triple: [Park Ward, vehicleTypeSpecializedIn, luxury saloons]
-
A.
vehicleFor
Indicates that one entity serves as the means of transportation or conveyance for another entity.
-
B.
vehicleType
Indicates the specific kind or category of vehicle associated with an entity (e.g., car, bus, bicycle).
-
C.
vehicleTypeFocus
Indicates that the relationship or action specifically concerns or emphasizes a particular type or category of vehicle.
-
D.
vehicleClassServed
chosen
Indicates the class or type of vehicle that a service, facility, or operation is designed to accommodate or serve.
-
E.
vehicleFamily
Indicates that two vehicles belong to the same family or category based on shared design, platform, or lineage.
- 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19a1401748190b77df0a45c2aeebf |
completed | April 29, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:19 p.m.