Triple
T18156688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porsche Supercup |
E434648
|
entity |
| Predicate | relationToPorsche |
P34778
|
FINISHED |
| Object | flagship customer racing series |
—
|
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: flagship customer racing series | Statement: [Porsche Supercup, relationToPorsche, flagship customer racing series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToPorsche Context triple: [Porsche Supercup, relationToPorsche, flagship customer racing series]
-
A.
relationToExecutive
Indicates a relationship or connection that an entity has to an executive, such as reporting lines, oversight, or affiliation.
-
B.
relationToVonMaur
Indicates a specified type of relationship or association that an entity has with Von Maur.
-
C.
relatedVehicle
Indicates that there exists an associated or connected vehicle that has a relevant relationship to the primary entity.
-
D.
relationToLeague
Indicates the type or nature of a team's or participant's association with a specific league (e.g., membership, affiliation, or standing).
-
E.
termRelationTo
chosen
Indicates a general relational association between one term and another, without specifying the exact nature of that relationship.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4debe27a88190bd76c6f78fcf1bd1 |
completed | April 19, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.