Triple
T25341095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senna Chicane |
E635413
|
entity |
| Predicate | hasTurnSequence |
P65957
|
FINISHED |
| Object | left-right combination |
—
|
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: left-right combination | Statement: [Senna Chicane, hasTurnSequence, left-right combination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTurnSequence Context triple: [Senna Chicane, hasTurnSequence, left-right combination]
-
A.
hasTurnStructure
Indicates that an interaction, game, or process is organized into discrete turns that participants take in a defined order.
-
B.
hasTurningMethod
Indicates that an entity employs or is associated with a specific method or technique for turning or rotating something.
-
C.
hasSequencePosition
Indicates that an element occupies a specific position or order within a sequence.
-
D.
hasTypicalSequence
chosen
Indicates that there is a usual or commonly occurring order or progression in which the related entities or events take place.
-
E.
hasAnimationSequencesBy
Indicates that an entity’s animation sequences are created, provided, or authored 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f498b6672881909d3257dc6b52caa3 |
completed | May 1, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:32 p.m.