Triple
T17108672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander-in-Chief, Pakistan Army |
E415167
|
entity |
| Predicate | firstHolderServiceStart |
P38523
|
FINISHED |
| Object | 1947 |
—
|
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: 1947 | Statement: [Commander-in-Chief, Pakistan Army, firstHolderServiceStart, 1947]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstHolderServiceStart Context triple: [Commander-in-Chief, Pakistan Army, firstHolderServiceStart, 1947]
-
A.
firstHolderEnd
Indicates that the specified entity is the one who initially held something and that this holding relationship has come to an end.
-
B.
firstHolderLifespan
Indicates the duration of life of the initial holder in a sequence of holders.
-
C.
firstHolderDate
Indicates the date on which an entity first became the holder or owner of another entity (e.g., an asset, title, or right).
-
D.
secondCreationFirstHolder
Indicates that the first entity is the original holder or owner of the second entity at the time of its creation.
-
E.
firstOfficeHolderStart
chosen
Indicates the date or time when the first person to hold a particular office or position began their term.
- 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.