Triple
T33073220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hairatan |
E846289
|
entity |
| Predicate | hasBorderCheckpointName |
P193492
|
FINISHED |
| Object | Hairatan border crossing |
—
|
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: Hairatan border crossing | Statement: [Hairatan, hasBorderCheckpointName, Hairatan border crossing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderCheckpointName Context triple: [Hairatan, hasBorderCheckpointName, Hairatan border crossing]
-
A.
hasBorderCheckpointOnOtherSide
Indicates that a border checkpoint is located on the opposite side of a boundary relative to a referenced point or entity.
-
B.
hasBorderMarkerType
Indicates that a border marker possesses or is classified by a specific type or category of border marker.
-
C.
hasBorderTerminus
Indicates that one entity serves as the endpoint or terminal location of another entity’s border or boundary.
-
D.
hasBorderCode
Indicates that there is an associated code or identifier specifying the type or status of a border between entities.
-
E.
hasBordersBy
Indicates that one entity shares a boundary or border with another entity.
- F. None of above. chosen
Provenance (4 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69fd485e0c20819099756b4fe39ac326 |
completed | May 8, 2026, 2:20 a.m. |
Created at: May 1, 2026, 1:25 a.m.