Triple
T15952984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Circuit de Spa-Francorchamps |
E386861
|
entity |
| Predicate | originalLayoutType |
P35487
|
FINISHED |
| Object | public road circuit |
—
|
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: public road circuit | Statement: [Circuit de Spa-Francorchamps, originalLayoutType, public road circuit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalLayoutType Context triple: [Circuit de Spa-Francorchamps, originalLayoutType, public road circuit]
-
A.
originalType
Indicates that one entity represents the initial or source type from which another entity is derived, transformed, or reclassified.
-
B.
originalStructureType
chosen
Indicates the type or category of the structure that an entity originally had before any changes or transformations.
-
C.
originalLocationType
Indicates the type or category of the place where something was originally located or came from.
-
D.
originalMode
Indicates that something preserves, reflects, or is associated with its initial or default mode of operation or state.
-
E.
laidOutBy
Indicates that one entity has been arranged, organized, or presented in a particular layout or structure by another entity.
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d37cd88190ab50760f1783e20c |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:53 a.m.