Triple
T11893749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senna S |
E282982
|
entity |
| Predicate | cornerComplexType |
P102111
|
FINISHED |
| Object | chicane-like sequence |
—
|
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: chicane-like sequence | Statement: [Senna S, cornerComplexType, chicane-like sequence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cornerComplexType Context triple: [Senna S, cornerComplexType, chicane-like sequence]
-
A.
partOfComplexType
Indicates that an entity functions as a component or member within a larger, composite structure or complex type.
-
B.
hasComplex
Indicates that one entity possesses, is associated with, or is part of a larger composite structure or complex formed with another entity.
-
C.
positionWithinComplex
Indicates that one entity is located inside or forms a component part of a larger complex or compound structure.
-
D.
cornerOfTriangle
Indicates that the subject is a vertex (corner point) belonging to a specific triangle.
-
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. 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8dd1172988190a2c13d37220f2f93 |
completed | April 10, 2026, 11:20 a.m. |
| PD | Predicate disambiguation | batch_69d8bb2fca4481909893f3428b0871ac |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8d399d58c81908dab572aa82426d7 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 8, 2026, 9:44 p.m.