Triple
T26224036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bahuda Yatra |
E655839
|
entity |
| Predicate | hasSecurityArrangementBy |
P8728
|
FINISHED |
| Object | Odisha Police |
—
|
NE NERFINISHED |
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: Odisha Police | Statement: [Bahuda Yatra, hasSecurityArrangementBy, Odisha Police]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecurityArrangementBy Context triple: [Bahuda Yatra, hasSecurityArrangementBy, Odisha Police]
-
A.
securityArrangementsBy
chosen
Indicates that one entity is responsible for providing, organizing, or overseeing security arrangements for another entity or situation.
-
B.
hasSecurityPresence
Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
-
C.
hasSecurityRegime
Indicates that an entity is governed, protected, or controlled by a particular security regime, framework, or set of security rules.
-
D.
hasSecurityAuthority
Indicates that one entity possesses the right or power to enforce, manage, or make decisions about security over another entity or resource.
-
E.
hasSecurityRelationship
Indicates a relationship in which one entity provides, manages, or is otherwise linked to the security or protection of 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 26, 2026, 8:57 p.m.