Triple
T23705477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People's Revolutionary Militia |
E585706
|
entity |
| Predicate | armedBranchType |
P91149
|
FINISHED |
| Object | civilian militia |
—
|
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: civilian militia | Statement: [People's Revolutionary Militia, armedBranchType, civilian militia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armedBranchType Context triple: [People's Revolutionary Militia, armedBranchType, civilian militia]
-
A.
armedForcesBranchNumber
Indicates the specific numerical designation or identifier assigned to a branch of the armed forces within a military organization.
-
B.
armedForcesBranchContext
Indicates the specific branch of a nation's armed forces within which a given military-related fact, role, or activity is situated.
-
C.
armedVariants
Indicates that one entity is a version or model of another that is equipped with weapons or enhanced armaments.
-
D.
armedBy
Indicates that one entity is supplied with weapons, equipment, or armaments by another entity.
-
E.
militaryBranchAssociatedWith
chosen
Indicates a relationship where an entity is connected to, or operates as part of, a specific branch of a military organization.
- 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_69e24904bd508190abfcb74855de2918 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b686ef50819090a85e3ed40cfba1 |
completed | April 29, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:53 p.m.