Triple
T22270314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peraltada corner |
E550456
|
entity |
| Predicate | layoutRole |
P147625
|
FINISHED |
| Object | transition from infield section to start-finish straight |
—
|
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: transition from infield section to start-finish straight | Statement: [Peraltada corner, layoutRole, transition from infield section to start-finish straight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: layoutRole Context triple: [Peraltada corner, layoutRole, transition from infield section to start-finish straight]
-
A.
layoutSupport
Indicates that one entity provides or enables structural or spatial arrangement capabilities for another entity.
-
B.
layoutOptions
Indicates how elements are arranged or positioned relative to each other within a given space or structure.
-
C.
layoutShape
Indicates a spatial or structural arrangement relationship where one entity defines or influences the geometric shape or configuration of another.
-
D.
visibilityRole
Indicates the role or level of access an entity has in determining what information or content is visible to others.
-
E.
layoutEngine
Indicates the rendering or layout system responsible for arranging and positioning elements within a visual or document structure.
- F. None of above. chosen
Provenance (4 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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f141bf53a481909e2c79de4144f332 |
completed | April 28, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:40 p.m.