Triple
T9325618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NOE (Nucleo Operativo Ecologico) |
E224377
|
entity |
| Predicate | lawEnforcementBodyType |
P7908
|
FINISHED |
| Object | military police |
—
|
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: military police | Statement: [NOE (Nucleo Operativo Ecologico), lawEnforcementBodyType, military police]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lawEnforcementBodyType Context triple: [NOE (Nucleo Operativo Ecologico), lawEnforcementBodyType, military police]
-
A.
typeOfLawEnforcement
chosen
Indicates that one entity is a specific kind or category of law enforcement associated with another entity.
-
B.
enforcementAgency
Indicates that one entity serves as the authority responsible for enforcing laws, rules, or regulations related to another entity.
-
C.
governmentBodyType
Indicates the classification or category of a governmental organization based on its structural or functional role.
-
D.
policeBureau
Indicates that an entity functions as or is associated with a police bureau or police department.
-
E.
lawEnforcementLabel
Indicates that an entity has been designated, tagged, or classified by a law enforcement authority for monitoring, identification, or investigative purposes.
- 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_69ca8427a0c08190b749831d5ea98f02 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd36f77c808190aa5489c4305fd67d |
completed | April 1, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cc7a643924819097f01144734901cf |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:39 p.m.