Triple
T38327467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chapel |
E1036827
|
entity |
| Predicate | onTrackLayout |
P22148
|
FINISHED |
| Object | Grand Prix Circuit layout of Silverstone |
—
|
LITERAL 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: Grand Prix Circuit layout of Silverstone | Statement: [Chapel, onTrackLayout, Grand Prix Circuit layout of Silverstone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onTrackLayout Context triple: [Chapel, onTrackLayout, Grand Prix Circuit layout of Silverstone]
-
A.
onLayout
Indicates that a layout-related event or process is occurring or has occurred for a given entity, typically involving the arrangement or positioning of its components.
-
B.
trackLayout
chosen
Indicates how the components or segments of a track are arranged and connected in relation to one another.
-
C.
movedToTrack
Indicates that an entity has changed its position or assignment from its previous location onto a specific track.
-
D.
trackOn
Indicates that one entity is physically positioned or moving along the surface or path of another, like a vehicle on a track or rails.
-
E.
positionInTrackList
Indicates the specific ordered place an item occupies within a track list.
- 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_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.