Triple
T22940857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bến Hải River |
E569723
|
entity |
| Predicate | usedAsBoundaryFrom |
P79571
|
FINISHED |
| Object | 1954 |
—
|
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: 1954 | Statement: [Bến Hải River, usedAsBoundaryFrom, 1954]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsBoundaryFrom Context triple: [Bến Hải River, usedAsBoundaryFrom, 1954]
-
A.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
B.
hasBoundaryInfluenceFrom
Indicates that the boundary or limits of one entity are affected, shaped, or determined by another entity.
-
C.
isPartOfLargerBoundary
Indicates that one boundary is contained within or forms a component of a larger encompassing boundary.
-
D.
previouslyPartOfBoundaryBetween
chosen
Indicates that something once formed part of the dividing line or border between two areas or entities, but no longer does so.
-
E.
hasBoundaryUnit
Indicates that one entity uses or is associated with a specific unit of measurement for its boundary or limit.
- 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_69e24590862c8190858f180ad302adab |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181394fec81909da791bb346dbd0a |
completed | April 29, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:45 p.m.