Triple
T17108677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander-in-Chief, Pakistan Army |
E415167
|
entity |
| Predicate | secondHolderServiceStart |
P125967
|
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, secondHolderServiceStart, 1948]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondHolderServiceStart Context triple: [Commander-in-Chief, Pakistan Army, secondHolderServiceStart, 1948]
-
A.
secondHolder
Indicates that an entity is the second person or party to hold or possess a particular item, role, title, or position in a sequence.
-
B.
secondCreationFirstHolder
Indicates that the first entity is the original holder or owner of the second entity at the time of its creation.
-
C.
secondSessionStart
Indicates the point in time when a second or subsequent session begins.
-
D.
secondHolderOccupation
Indicates the occupation or job role held by the second participant in the relationship.
-
E.
secondHolderGivenName
Indicates that the given name specified belongs to the second holder in a multi-holder relationship or record.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e37542d060819082aa73948eb8ebd4 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:35 a.m.