Triple
T24133130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tumen-gang River |
E598007
|
entity |
| Predicate | sourceLocatedOnBorderOf |
P67212
|
FINISHED |
| Object | China and North Korea |
—
|
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: China and North Korea | Statement: [Tumen-gang River, sourceLocatedOnBorderOf, China and North Korea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceLocatedOnBorderOf Context triple: [Tumen-gang River, sourceLocatedOnBorderOf, China and North Korea]
-
A.
liesOnBorderOf
chosen
Indicates that one entity is located along or directly adjacent to the boundary line separating it from another entity.
-
B.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
C.
operatesOnBorderWith
Indicates that one entity conducts activities or exerts influence along or across the shared border it has with another entity.
-
D.
sourceLocatedOn
Indicates that the source entity is physically situated on the surface or area of the target entity.
-
E.
borderPoint
Indicates a point that lies on the boundary between two regions or entities.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df79bfd08190970ed1b3f14ebc8b |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:26 p.m.