Triple
T23781489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yalu River Broken Bridge |
E587825
|
entity |
| Predicate | extendsFromBank |
P142266
|
FINISHED |
| Object | Chinese bank of Yalu River |
—
|
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: Chinese bank of Yalu River | Statement: [Yalu River Broken Bridge, extendsFromBank, Chinese bank of Yalu River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendsFromBank Context triple: [Yalu River Broken Bridge, extendsFromBank, Chinese bank of Yalu River]
-
A.
turnBanking
Indicates that an entity is executing a turning maneuver that involves banking or tilting laterally, typically as part of directional change.
-
B.
usesBanking
Indicates that one entity makes use of the banking services, facilities, or systems provided by another entity.
-
C.
hasBankOn
chosen
Indicates that one entity is located on or alongside the bank (edge) of another entity, typically a river, lake, or similar body.
-
D.
hasBank
Indicates that one entity possesses, is associated with, or is served by a particular bank (such as a financial institution or river bank).
-
E.
trackBanking
Indicates monitoring, recording, or managing banking-related activities or transactions associated with an entity.
- 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_69e2490f4ad48190b690878eec3596c6 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c62d7c608190b5fd0cf35f5faf42 |
completed | April 29, 2026, 8:49 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:16 p.m.