Triple
T25086521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saif al-Adil |
E628336
|
entity |
| Predicate | reportedLocation |
P158771
|
FINISHED |
| Object | Afghanistan-Pakistan border region |
—
|
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: Afghanistan-Pakistan border region | Statement: [Saif al-Adil, reportedLocation, Afghanistan-Pakistan border region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportedLocation Context triple: [Saif al-Adil, reportedLocation, Afghanistan-Pakistan border region]
-
A.
reportedLocation
chosen
Indicates that an entity has been specified or recorded as being at a particular location, typically based on a report or observation rather than direct verification.
-
B.
createdAtLocation
Indicates the place or location where an entity was originally created or brought into existence.
-
C.
locationWhenGiven
Indicates the place where an entity is located at the time it is given or transferred to another entity.
-
D.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified by another entity.
-
E.
propertyLocation
Indicates the geographical place or address where a property is situated or found.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 6:23 a.m.