Triple
T20737067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suifenhe |
E509738
|
entity |
| Predicate | borderPortType |
P47626
|
FINISHED |
| Object | land port |
—
|
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: land port | Statement: [Suifenhe, borderPortType, land port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderPortType Context triple: [Suifenhe, borderPortType, land port]
-
A.
borderPostType
chosen
Indicates the specific kind or classification of a border post associated with a boundary or crossing point.
-
B.
borderTerminus
Indicates the endpoint location where a border between two areas or entities begins or ends.
-
C.
borderStationFor
Indicates that a particular border station serves, monitors, or is responsible for a specific border crossing or boundary segment.
-
D.
borderServiceCategory
Indicates a classification relationship where a border-related service is assigned to a specific service category or type.
-
E.
borderDefinedBy
Indicates that the boundary or limit of one entity is determined, shaped, or delineated by another 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_69e0b4c589c08190834fb5d86d0efa2b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c20ac6e881908524be890be699e7 |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:32 p.m.