Triple
T26413815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heihe–Blagoveshchensk ferry |
E664030
|
entity |
| Predicate | operatesOnSectionOf |
P83224
|
FINISHED |
| Object | Sino–Russian border |
—
|
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: Sino–Russian border | Statement: [Heihe–Blagoveshchensk ferry, operatesOnSectionOf, Sino–Russian border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesOnSectionOf Context triple: [Heihe–Blagoveshchensk ferry, operatesOnSectionOf, Sino–Russian border]
-
A.
appliesToSectionOf
Indicates that something is relevant or applicable specifically to a particular section or subsection of a larger whole.
-
B.
operatesOnRouteSection
chosen
Indicates that an entity performs its function or service along, within, or in connection with a specific route section.
-
C.
usesSectionOf
Indicates that one entity makes use of a specific section or part of another entity.
-
D.
isOnSectionOf
Indicates that one entity is located on, or positioned along, a specific segment or subsection of another entity.
-
E.
operatesInSegment
Indicates that an entity conducts its activities or provides its services within a specified market or operational segment.
- 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_69ee883a04ec81908883c4559f8c7e24 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: April 26, 2026, 11:40 p.m.