Triple
T20103585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nettuno V6 |
E496609
|
entity |
| Predicate | vehicleClassApplication |
P109335
|
FINISHED |
| Object | supercar |
—
|
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: supercar | Statement: [Nettuno V6, vehicleClassApplication, supercar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleClassApplication Context triple: [Nettuno V6, vehicleClassApplication, supercar]
-
A.
applicationVehicle
Indicates a relationship where a particular vehicle is used, specified, or associated within the context of an application or application process.
-
B.
mainVehicleClass
chosen
Indicates the primary category or type of vehicle to which an entity chiefly belongs.
-
C.
vehicleType
Indicates the specific kind or category of vehicle associated with an entity (e.g., car, bus, bicycle).
-
D.
vehicleEligibility
Indicates whether a given vehicle satisfies the required conditions or criteria to be considered eligible for a specified purpose or program.
-
E.
vehicleRegistrationCategory
Indicates the classification or type of registration assigned to a vehicle under a specific regulatory or administrative scheme.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6667170a4819085d07a4188ded541 |
completed | April 20, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:27 p.m.