Triple
T31380750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bandimere Speedway |
E800445
|
entity |
| Predicate | hasStagingLanes |
P2128
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Bandimere Speedway, hasStagingLanes, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStagingLanes Context triple: [Bandimere Speedway, hasStagingLanes, yes]
-
A.
hasCheckInLanes
Indicates that an entity is equipped with or provides designated lanes or areas where check-in processes (such as registration or ticketing) take place.
-
B.
hasLanes
chosen
Indicates that an entity, such as a road or pathway, is divided into one or more distinct lanes for traffic or movement.
-
C.
hasStageVersion
Indicates that one entity is a specific stage, phase, or version within the lifecycle or progression of another entity.
-
D.
hasFlexibleStaging
Indicates that an entity supports adaptable or variable staging arrangements, allowing stages or phases to be configured or adjusted as needed.
-
E.
hasStageRange
Indicates that there is a defined range of stages or phases associated with an entity, from a starting stage to an ending stage.
- 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_69f224e84da08190abfc2f17494a33c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69feaa483fcc81909d8a46b38a8717bf |
completed | May 9, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69fea8c9d45c81908ccc8619e5fefac1 |
completed | May 9, 2026, 3:23 a.m. |
Created at: April 29, 2026, 9:18 p.m.