Triple
T18156349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casino Square |
E434639
|
entity |
| Predicate | hasTurnConfiguration |
P13644
|
FINISHED |
| Object | complex of medium-speed corners |
—
|
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: complex of medium-speed corners | Statement: [Casino Square, hasTurnConfiguration, complex of medium-speed corners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTurnConfiguration Context triple: [Casino Square, hasTurnConfiguration, complex of medium-speed corners]
-
A.
hasConfiguration
chosen
Indicates that an entity is associated with or defined by a particular configuration or setup.
-
B.
hasTurningMethod
Indicates that an entity employs or is associated with a specific method or technique for turning or rotating something.
-
C.
hasTailConfiguration
Indicates the specific type or arrangement of an entity’s tail or tail-like structure.
-
D.
hasSetting
Indicates that an entity takes place, occurs, or exists within a particular environment, context, or location.
-
E.
hasRound
Indicates that an entity possesses, includes, or is associated with a particular round (e.g., a round of an event, game, or process).
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4debe27a88190bd76c6f78fcf1bd1 |
completed | April 19, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.