Triple
T8802737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CISF |
E209449
|
entity |
| Predicate | providesSecurityTo |
P8728
|
FINISHED |
| Object | Public sector undertakings |
—
|
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: Public sector undertakings | Statement: [CISF, providesSecurityTo, Public sector undertakings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesSecurityTo Context triple: [CISF, providesSecurityTo, Public sector undertakings]
-
A.
providesProtectionAgainst
Indicates that one entity serves to guard, shield, or defend another entity from a specified harm, threat, or adverse effect.
-
B.
providesProtectionIn
Indicates that one entity offers protection or safeguarding to another entity within a specified context, location, or situation.
-
C.
securityGuarantee
Indicates a commitment by one party to protect or defend another party against specified threats or risks.
-
D.
securityArrangementsBy
chosen
Indicates that one entity is responsible for providing, organizing, or overseeing security arrangements for another entity or situation.
-
E.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
- 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_69ca836320e48190b5cf585b90a322c4 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fbb5b108190a9f889d40aa20521 |
completed | March 31, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:44 p.m.