Triple
T33063410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dogharun |
E846031
|
entity |
| Predicate | borderCrossingPair |
P108638
|
FINISHED |
| Object | Islam Qala 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: Islam Qala border crossing | Statement: [Dogharun, borderCrossingPair, Islam Qala border crossing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCrossingPair Context triple: [Dogharun, borderCrossingPair, Islam Qala border crossing]
-
A.
borderCrossingStatus
Indicates the current state or outcome of an entity’s attempt to cross a border (e.g., allowed, denied, pending, or completed).
-
B.
borderCrossingArea
chosen
Indicates an area specifically designated for crossing a border between two jurisdictions or territories.
-
C.
borderCrossingDirectionTo
Indicates the direction in which a border crossing occurs from one side or territory to another.
-
D.
borderCrossingRouteTo
Indicates a route or path used to travel across a border from one place or jurisdiction to another.
-
E.
borderCrossingMode
Indicates the means or method by which a border is crossed between territories or jurisdictions.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff1e3e13c08190bb8990c44716b746 |
completed | May 9, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_69ff1dfcaf2c8190aaf2b428d57b7782 |
completed | May 9, 2026, 11:43 a.m. |
Created at: May 1, 2026, 1:25 a.m.