Triple
T24971201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porsche Carrera Cup Germany |
E624893
|
entity |
| Predicate | driverLevel |
P4144
|
FINISHED |
| Object | young aspiring GT drivers |
—
|
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: young aspiring GT drivers | Statement: [Porsche Carrera Cup Germany, driverLevel, young aspiring GT drivers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: driverLevel Context triple: [Porsche Carrera Cup Germany, driverLevel, young aspiring GT drivers]
-
A.
driverType
Indicates the category or role of a driver associated with an entity or activity (e.g., primary, backup, commercial, etc.).
-
B.
driveType
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
C.
trainingLevel
chosen
Indicates the degree or stage of training or skill development that an entity has attained.
-
D.
driverAcademy
Indicates a relationship where an academy provides training or education to individuals to become drivers or improve their driving skills.
-
E.
driverRequirement
Indicates that a certain driver, qualification, or driving-related condition is required for an entity to perform or be associated with a particular role, task, or operation.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 6:01 a.m.