Triple
T17108673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander-in-Chief, Pakistan Army |
E415167
|
entity |
| Predicate | firstHolderServiceEnd |
P17301
|
FINISHED |
| Object | 1948 |
—
|
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: 1948 | Statement: [Commander-in-Chief, Pakistan Army, firstHolderServiceEnd, 1948]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstHolderServiceEnd Context triple: [Commander-in-Chief, Pakistan Army, firstHolderServiceEnd, 1948]
-
A.
firstHolderEnd
chosen
Indicates that the specified entity is the one who initially held something and that this holding relationship has come to an end.
-
B.
firstHolderDate
Indicates the date on which an entity first became the holder or owner of another entity (e.g., an asset, title, or right).
-
C.
firstHolderLifespan
Indicates the duration of life of the initial holder in a sequence of holders.
-
D.
firstHolderParty
Indicates that the referenced party is the initial or original holder in the specified relationship or arrangement.
-
E.
lastHolder
Indicates that the subject is the most recent entity to have possessed, owned, or held the object.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc2906a081909d0d43cf04319f52 |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.