Triple
T14482711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fernando Alonso |
E359150
|
entity |
| Predicate | droveForTeam |
P60038
|
FINISHED |
| Object | McLaren |
E737468
|
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 | Statement: [Fernando Alonso, droveForTeam, McLaren]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: McLaren Context triple: [Fernando Alonso, droveForTeam, McLaren]
-
A.
McLaren Automotive
McLaren Automotive is a British high-performance sports car and supercar manufacturer renowned for its Formula 1–derived engineering and cutting-edge design.
-
B.
McLaren Group
chosen
McLaren Group is a British holding company best known for owning the McLaren Formula 1 team and the McLaren Automotive supercar brand.
-
C.
MacLaren
MacLaren is a Scottish surname historically linked to Clan MacLaren of the Scottish Highlands.
-
D.
Lotus F1 Team
Lotus F1 Team was a British Formula One constructor and racing team that competed in the FIA Formula One World Championship in the early 2010s.
-
E.
Jaguar Racing
Jaguar Racing was a British Formula One team and motorsport outfit that competed in F1 in the early 2000s as the works team of the Jaguar automotive brand.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924bc548819087a2f693840d7426 |
completed | April 14, 2026, 7:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd64a41a8c819081a3eaabbe66577a |
completed | May 8, 2026, 4:20 a.m. |
Created at: April 10, 2026, 1:20 a.m.