Triple
T31520123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emir Abdur Rahman Khan |
E804184
|
entity |
| Predicate | dateSignedDurandLine |
P126595
|
FINISHED |
| Object | 1893 |
—
|
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: 1893 | Statement: [Emir Abdur Rahman Khan, dateSignedDurandLine, 1893]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateSignedDurandLine Context triple: [Emir Abdur Rahman Khan, dateSignedDurandLine, 1893]
-
A.
dateSigned
Indicates the specific date on which an agreement, document, or contract was formally signed.
-
B.
signatureLine
Indicates that an entity serves as a designated place or line where a signature is written or recorded.
-
C.
documentSignedBy
Indicates that a document has been formally signed or authorized by a specific entity.
-
D.
borderTreatySignedOn
chosen
Indicates that a formal agreement establishing or modifying a border between entities was signed on a specific date.
-
E.
signedTreatyAt
Indicates that an entity formally entered into and endorsed a treaty at a specific location.
- 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 9:55 p.m.