Triple
T29337342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Protection Group Act, 1988 |
E743944
|
entity |
| Predicate | legalStatusOfSPG |
P2250
|
FINISHED |
| Object | armed force of the Union |
—
|
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: armed force of the Union | Statement: [Special Protection Group Act, 1988, legalStatusOfSPG, armed force of the Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusOfSPG Context triple: [Special Protection Group Act, 1988, legalStatusOfSPG, armed force of the Union]
-
A.
hasLegalStatus
chosen
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
B.
regulatedStatusOf
Indicates that one entity has regulatory authority or control over the status or condition of another entity.
-
C.
sponsorStatus
Indicates the current state or condition of an entity’s sponsorship relationship, such as whether it is active, pending, or inactive.
-
D.
legalStatusOfAuthority
Indicates the legal status or standing that a particular authority holds within a given legal or regulatory framework.
-
E.
legalStatusAtApproval
Indicates the legal status or classification an entity held at the time it was formally approved.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: April 28, 2026, 1:31 p.m.