Triple
T11641756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malakand Pass |
E276676
|
entity |
| Predicate | hasCheckPost |
P30109
|
FINISHED |
| Object | Malakand Levies check post |
—
|
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: Malakand Levies check post | Statement: [Malakand Pass, hasCheckPost, Malakand Levies check post]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCheckPost Context triple: [Malakand Pass, hasCheckPost, Malakand Levies check post]
-
A.
hasIntegratedCheckPost
Indicates that one entity includes or contains a check post that is functionally integrated within it.
-
B.
hadCheckpoint
Indicates that an entity passed through, reached, or was associated with a specific checkpoint at some point in time.
-
C.
hasCheckpoint
chosen
Indicates that an entity includes, contains, or is associated with one or more intermediate control or verification points within its structure, process, or path.
-
D.
checkedBy
Indicates that an entity has been examined, verified, or reviewed by another entity.
-
E.
isKeyPostIn
Indicates that a post or position is a central, strategically important element within a specified organization, structure, or context.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a260ab488190ab1c00d9850f3096 |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.