Triple
T34577881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BQE |
E887808
|
entity |
| Predicate | boroughsTraversed |
P21450
|
FINISHED |
| Object | Brooklyn |
—
|
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: Brooklyn | Statement: [BQE, boroughsTraversed, Brooklyn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boroughsTraversed Context triple: [BQE, boroughsTraversed, Brooklyn]
-
A.
urbanDistrictsTraversed
Indicates that a route, path, or entity passes through or crosses one or more urban districts.
-
B.
travelsThrough
Indicates that something moves along, passes across, or is routed via a particular path, medium, or location.
-
C.
regionsVisited
Indicates that an entity has traveled to, been present in, or otherwise visited specific geographic regions.
-
D.
boroughServed
Indicates that a given entity (such as a facility, service, or route) serves or provides coverage to a specific borough.
-
E.
passesThroughBorough
chosen
Indicates that something (such as a route, line, or path) traverses or goes through a particular borough.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7209b45e48190b08a5085d90865e5 |
completed | May 3, 2026, 10:16 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:03 a.m.