Triple
T4187068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief of the Army Staff (India) |
E88336
|
entity |
| Predicate | isSingleServiceChief |
P39804
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Chief of the Army Staff (India), isSingleServiceChief, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSingleServiceChief Context triple: [Chief of the Army Staff (India), isSingleServiceChief, true]
-
A.
hasServiceChief
chosen
Indicates that one entity serves as the chief or head responsible for overseeing the services of another entity.
-
B.
isCivilianOffice
Indicates that an office or position is non-military and belongs to the civilian sphere of authority or administration.
-
C.
isOfficerOf
Indicates that one entity holds an official position, role, or office within another entity (such as an organization, group, or institution).
-
D.
isHeadOf
Indicates that one entity holds the leading or principal authority position over another entity, such as an organization, group, or department.
-
E.
commanderAlsoServesAs
Indicates that the person who holds a commander role simultaneously fulfills one or more additional official roles or positions.
- 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_69aed9477e8c81908bcb862d2db55b1d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af04b009dc8190abda3f149a5b16fa |
completed | March 9, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69af01935064819096b7619f42e164dd |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.