Triple
T32151028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milicias de Tropas Territoriales |
E821157
|
entity |
| Predicate | isCivilianBased |
P173640
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Milicias de Tropas Territoriales, isCivilianBased, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCivilianBased Context triple: [Milicias de Tropas Territoriales, isCivilianBased, true]
-
A.
isCivilian
Indicates that an entity is a non-military, non-combatant individual in the context of a given situation or system.
-
B.
isCivilianOffice
Indicates that an office or position is non-military and belongs to the civilian sphere of authority or administration.
-
C.
isCivilMilitary
Indicates that an entity or relationship involves both civilian and military components or functions.
-
D.
isCivilianCommunityFor
Indicates that one entity functions as a civilian community associated with, serving, or surrounding another entity.
-
E.
hasCivilianClass
Indicates that an entity is associated with or belongs to a particular civilian classification or category.
- F. None of above. chosen
Provenance (4 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b9ebdf888190828cd457f790497e |
completed | May 3, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:31 a.m.