Triple
T38337147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbey |
E1037988
|
entity |
| Predicate | isOneOfOpeningCornersOf |
P42380
|
FINISHED |
| Object | Silverstone Circuit |
—
|
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 Circuit | Statement: [Abbey, isOneOfOpeningCornersOf, Silverstone Circuit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOneOfOpeningCornersOf Context triple: [Abbey, isOneOfOpeningCornersOf, Silverstone Circuit]
-
A.
hasCorner
chosen
Indicates that one entity possesses or includes a corner that is part of or associated with another entity.
-
B.
hasTypeOfCorner
Indicates that one entity possesses or is characterized by a specific kind or category of corner.
-
C.
hasCornerCount
Indicates that an entity is associated with a specific number of corners.
-
D.
hasCentralOpeningType
Indicates that an entity possesses a central opening characterized by a specific type or form.
-
E.
locatedAtCornerOf
Indicates that one entity is positioned at or forms the corner where two or more boundaries, edges, or intersecting paths meet.
- 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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:30 p.m.