Triple
T26666988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nyck de Vries |
E672211
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object |
2019 FIA Formula 2 Champion
The 2019 FIA Formula 2 Champion is Dutch racing driver Nyck de Vries, who later progressed to compete in Formula E and Formula 1.
|
E1734396
|
NE 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: 2019 FIA Formula 2 Champion | Statement: [Nyck de Vries, title, 2019 FIA Formula 2 Champion]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: 2019 FIA Formula 2 Champion Triple: [Nyck de Vries, title, 2019 FIA Formula 2 Champion]
Generated description
The 2019 FIA Formula 2 Champion is Dutch racing driver Nyck de Vries, who later progressed to compete in Formula E and Formula 1.
Provenance (5 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_69eecda00a9c8190b2691f4d89db03b6 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f616c4dda8819088c175f27c5f0961 |
completed | May 2, 2026, 3:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a11ec4eb7e88190bafb81ed09480ea2 |
completed | May 23, 2026, 6:05 p.m. |
| NEDg | Description generation | batch_6a11ed11cca08190b0700be2359851d0 |
completed | May 23, 2026, 6:08 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a11ee05a1e08190a2828bc52ba17279 |
completed | May 23, 2026, 6:12 p.m. |
Created at: April 27, 2026, 3:10 a.m.