Triple
T33315188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Circuito de Jerez-Ángel Nieto |
E852996
|
entity |
| Predicate | directionOfLayout |
P29448
|
FINISHED |
| Object | clockwise |
—
|
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: clockwise | Statement: [Circuito de Jerez-Ángel Nieto, directionOfLayout, clockwise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionOfLayout Context triple: [Circuito de Jerez-Ángel Nieto, directionOfLayout, clockwise]
-
A.
styleOrientation
Indicates the general stylistic direction or aesthetic approach that characterizes how something is designed, presented, or expressed.
-
B.
directionalConfiguration
chosen
Indicates a specific spatial or directional arrangement that one entity has relative to another.
-
C.
orientationType
Indicates the specific kind or category of orientation relationship that exists between entities (such as spatial, directional, or alignment-based orientation).
-
D.
orientationPrinciple
Indicates the guiding rule or standard that directs how something is positioned, aligned, or oriented in relation to other things.
-
E.
lineLayout
Indicates how elements are arranged or positioned along a line or linear sequence in a layout.
- 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_69f349679fd8819093b9b40e989440e3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: May 1, 2026, 1:33 a.m.