Triple
T11788612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gendarmerie of the Kingdom of Yugoslavia |
E280333
|
entity |
| Predicate | isMilitarized |
P101588
|
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: [Gendarmerie of the Kingdom of Yugoslavia, isMilitarized, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMilitarized Context triple: [Gendarmerie of the Kingdom of Yugoslavia, isMilitarized, true]
-
A.
wasMilitarized
Indicates that an entity underwent a process of being organized, equipped, or adapted for military use or purposes.
-
B.
wasMilitarizedDuring
Indicates that an entity transitioned to or adopted a military character, role, or control during a specified time period or event.
-
C.
isCivilMilitary
Indicates that an entity or relationship involves both civilian and military components or functions.
-
D.
hasMilitaryType
Indicates that an entity is associated with or classified under a specific military category, role, or type.
-
E.
civilOrMilitary
Indicates that something is classified as either civil (non-military) or military in nature or function.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a587c2d881909297c3a6c7d26080 |
completed | April 10, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69d8a2491f048190853239bc05090bf4 |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:42 p.m.