Triple
T18041078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civil Nuclear Constabulary |
E431653
|
entity |
| Predicate | isArmedForce |
P81775
|
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: [Civil Nuclear Constabulary, isArmedForce, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isArmedForce Context triple: [Civil Nuclear Constabulary, isArmedForce, true]
-
A.
hasArmedForces
Indicates that an entity possesses or maintains organized military forces under its control.
-
B.
isRegularArmyUnit
Indicates that the entity functions as a formal, organized military unit within a country's regular (non-irregular) armed forces.
-
C.
isMilitaryOfficer
Indicates that the subject holds an official position as an officer within a military organization.
-
D.
isUnifiedMilitaryOf
Indicates that an entity serves as the single, consolidated military force representing or defending another entity (such as a state, alliance, or organization).
-
E.
hasMilitaryType
chosen
Indicates that an entity is associated with or classified under a specific military category, role, or type.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4bfee78048190b3fada0eb3d28c77 |
completed | April 19, 2026, 11:43 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.