Triple
T27673718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azumabashi |
E697725
|
entity |
| Predicate | locatedNearBridge |
P19223
|
FINISHED |
| Object | Komagata Bridge |
—
|
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: Komagata Bridge | Statement: [Azumabashi, locatedNearBridge, Komagata Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedNearBridge Context triple: [Azumabashi, locatedNearBridge, Komagata Bridge]
-
A.
situatedNextTo
Indicates that one entity is located immediately beside another, with no significant separation between them.
-
B.
hasNearbyBridge
chosen
Indicates that one entity is located close to a bridge associated with or relevant to it.
-
C.
locatedAcrossRiverFrom
Indicates that one entity is situated on the opposite side of a river relative to another entity.
-
D.
locatedInBayOf
Indicates that something is situated within or directly on a specific bay.
-
E.
locatedNearCountry
Indicates that one entity is geographically situated close to the borders or territory of a specified country.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ff14d596e88190be5263b7f96a96cd |
completed | May 9, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_69ff13f0208081909369aeb3b77a6b1f |
completed | May 9, 2026, 11:01 a.m. |
Created at: April 27, 2026, 2:42 p.m.