Triple
T29526241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DGAR |
E749075
|
entity |
| Predicate | abbreviationForPositionIn |
P44634
|
FINISHED |
| Object | Indian security forces |
—
|
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: Indian security forces | Statement: [DGAR, abbreviationForPositionIn, Indian security forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abbreviationForPositionIn Context triple: [DGAR, abbreviationForPositionIn, Indian security forces]
-
A.
rankAbbreviation
chosen
Indicates that one term is an abbreviated form of a rank or title corresponding to another term.
-
B.
commonAbbreviationPlacement
Indicates that one form is commonly used as an abbreviation for another in typical writing or notation.
-
C.
shortForPositionIn
Indicates that one entity serves as an abbreviated or shortened form specifically for the position or role denoted by another entity.
-
D.
abbreviationOrShortForm
Indicates that one term is an abbreviation or shortened form of another term.
-
E.
abbreviationUsedFor
Indicates that a particular shortened form or acronym is used to represent or stand in for a longer term, name, or expression.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 4:46 p.m.