Triple

T32424751
Position Surface form Disambiguated ID Type / Status
Subject Japanese Grand Prix E828547 entity
Predicate hasCorner P42380 FINISHED
Object 130R at Suzuka
130R at Suzuka is a famously fast and challenging high-speed left-hand corner at Japan’s Suzuka Circuit, renowned for testing drivers’ courage and car stability in Formula 1.
E2006033 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: 130R at Suzuka | Statement: [Japanese Grand Prix, hasCorner, 130R at Suzuka]
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: 130R at Suzuka
Triple: [Japanese Grand Prix, hasCorner, 130R at Suzuka]
Generated description
130R at Suzuka is a famously fast and challenging high-speed left-hand corner at Japan’s Suzuka Circuit, renowned for testing drivers’ courage and car stability in 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_69f3491b28bc8190b75cea7a507f337b completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c286ac288190843dac21651babd0 completed May 3, 2026, 3:35 a.m.
NED1 Entity disambiguation (via context triple) batch_6a344f28cc3c8190894ce0c64aca697d completed June 18, 2026, 8:03 p.m.
NEDg Description generation batch_6a344ff6fd188190b5c585e81427a37b completed June 18, 2026, 8:07 p.m.
NED2 Entity disambiguation (via description) batch_6a3450d7fb488190b39c09e0761cb81c completed June 18, 2026, 8:11 p.m.
Created at: May 1, 2026, 12:54 a.m.