Triple
T10296759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nihonbashi |
E241509
|
entity |
| Predicate | bridgeCompleted |
P92972
|
FINISHED |
| Object | 1911 (current stone Nihonbashi Bridge) |
—
|
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: 1911 (current stone Nihonbashi Bridge) | Statement: [Nihonbashi, bridgeCompleted, 1911 (current stone Nihonbashi Bridge)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeCompleted Context triple: [Nihonbashi, bridgeCompleted, 1911 (current stone Nihonbashi Bridge)]
-
A.
bridgeStatus
Indicates the current operational condition or availability state of a bridge (e.g., open, closed, restricted).
-
B.
bridgeName
Indicates the designated name assigned to a specific bridge.
-
C.
bridgeOpened
Indicates that a bridge has transitioned from a closed or inactive state to being open and available for use.
-
D.
bridgeUsed
Indicates that a bridge is utilized or traversed by an entity to cross between two locations or points.
-
E.
bridgeCarries
Indicates that a bridge serves as a route or support structure for transporting or conveying something (such as vehicles, pedestrians, or utilities) across an obstacle.
- F. None of above. chosen
Provenance (4 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2ebd258819099fadddcd13099fc |
completed | April 7, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f35e548190be3b4d92d65d2d20 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d29d7cf08190acd70cee634c5cdb |
completed | April 7, 2026, 9:47 a.m. |
Created at: April 6, 2026, 11:43 a.m.