Triple
T14787552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Police (India) |
E347566
|
entity |
| Predicate | typeOfPolicing |
P7908
|
FINISHED |
| Object | coastal policing |
—
|
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: coastal policing | Statement: [Marine Police (India), typeOfPolicing, coastal policing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPolicing Context triple: [Marine Police (India), typeOfPolicing, coastal policing]
-
A.
policingModel
Indicates the approach, strategy, or framework used to organize and conduct policing activities or law enforcement operations.
-
B.
typeOfLawEnforcement
chosen
Indicates that one entity is a specific kind or category of law enforcement associated with another entity.
-
C.
policeControl
Indicates that one entity exercises authoritative oversight, regulation, or enforcement power over another, as a police force does over people or areas under its jurisdiction.
-
D.
policeSystem
Indicates a relationship where an entity functions as, belongs to, or is governed by a system of law enforcement or policing.
-
E.
lawEnforcementLevel
Indicates the degree or intensity of law enforcement presence, activity, or strictness applied in a given context.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decaa083e481908336d58d026eec32 |
completed | April 14, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.