Triple

T29207981
Position Surface form Disambiguated ID Type / Status
Subject McLaren 720S E740466 entity
Predicate successor P78 FINISHED
Object McLaren 750S
The McLaren 750S is a high-performance British supercar that evolves the 720S with more power, reduced weight, and sharpened aerodynamics for enhanced track and road capability.
E1895271 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: McLaren 750S | Statement: [McLaren 720S, successor, McLaren 750S]
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: McLaren 750S
Triple: [McLaren 720S, successor, McLaren 750S]
Generated description
The McLaren 750S is a high-performance British supercar that evolves the 720S with more power, reduced weight, and sharpened aerodynamics for enhanced track and road capability.

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_69f07cb974108190b7e86ca489a6ebb6 completed April 28, 2026, 9:24 a.m.
NER Named-entity recognition batch_69f66402f5348190be752c897f8e5e2d completed May 2, 2026, 8:52 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2721ce61f48190aa594f4a1a13e41f completed June 8, 2026, 8:10 p.m.
NEDg Description generation batch_6a2722e635488190b4dd3cf0e212f790 completed June 8, 2026, 8:15 p.m.
NED2 Entity disambiguation (via description) batch_6a2727b3fa008190a3d9bb95a065af14 completed June 8, 2026, 8:36 p.m.
Created at: April 28, 2026, 12:10 p.m.