Triple
T26386552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bricktown Water Taxi |
E663295
|
entity |
| Predicate | operatesWithinDistrict |
P128240
|
FINISHED |
| Object | Bricktown Canal corridor |
—
|
NE NERFINISHED |
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: Bricktown Canal corridor | Statement: [Bricktown Water Taxi, operatesWithinDistrict, Bricktown Canal corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesWithinDistrict Context triple: [Bricktown Water Taxi, operatesWithinDistrict, Bricktown Canal corridor]
-
A.
occursInDistrict
chosen
Indicates that an event or activity takes place within the boundaries of a specific district.
-
B.
meetsInDistrict
Indicates that two or more entities hold a meeting within the boundaries of a specified administrative district.
-
C.
appliesToDistrict
Indicates that something (such as a rule, policy, or condition) is relevant or applicable to a specific district.
-
D.
appliedInDistrict
Indicates that an application or action was submitted or carried out within a specific administrative district.
-
E.
basedInDistrict
Indicates that an entity is located or has its primary base of operations within a specific administrative district.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: April 26, 2026, 11:22 p.m.