Triple
T15841992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SRO Motorsports Group |
E384121
|
entity |
| Predicate | carCategory |
P1776
|
FINISHED |
| Object | GT3 cars |
—
|
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: GT3 cars | Statement: [SRO Motorsports Group, carCategory, GT3 cars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carCategory Context triple: [SRO Motorsports Group, carCategory, GT3 cars]
-
A.
vehicleType
chosen
Indicates the specific kind or category of vehicle associated with an entity (e.g., car, bus, bicycle).
-
B.
vehicleFamily
Indicates that two vehicles belong to the same family or category based on shared design, platform, or lineage.
-
C.
intendedVehicleClass
Indicates that one entity is designed or specified to be used with, or is appropriate for, a particular class or category of vehicle.
-
D.
vehicleRegistrationCategory
Indicates the classification or type of registration assigned to a vehicle under a specific regulatory or administrative scheme.
-
E.
vehicleStandard
Indicates that something complies with, or is defined according to, a specified vehicle-related standard or regulatory specification.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e88ff08190a1035269e8fdaa6a |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005434ed88190baf11c169da3cf29 |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:50 a.m.