Triple
T38327818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Circuit |
E1036837
|
entity |
| Predicate | sharesPitLaneWith |
P130328
|
FINISHED |
| Object | Silverstone National Pit Lane |
—
|
NE NERFINISHED |
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: Silverstone National Pit Lane | Statement: [National Circuit, sharesPitLaneWith, Silverstone National Pit Lane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesPitLaneWith Context triple: [National Circuit, sharesPitLaneWith, Silverstone National Pit Lane]
-
A.
pitLaneSharedWith
chosen
Indicates that two racing pit lanes are configured so that they are used jointly or overlap in access or operation.
-
B.
hasPitLane
Indicates that a racing circuit, track, or similar facility includes a designated pit lane area for vehicle servicing and related activities.
-
C.
sharesChassisWith
Indicates that two entities are built on the same underlying structural platform or frame.
-
D.
sharesLineUpWith
Indicates that two entities participate together in the same lineup or roster at the same time.
-
E.
sharesPodiumWith
Indicates that two or more participants occupy the winners’ podium together in the same event or ceremony.
- 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_69f76e1c16fc8190bde982289dd5106b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00c9ddd62881909859a36b114a4132 |
completed | May 10, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_6a00c939b88881909d5353db4265e572 |
completed | May 10, 2026, 6:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.