Triple
T26936805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cona B |
E678406
|
entity |
| Predicate | militaryAdministration |
P16398
|
FINISHED |
| Object | Yugoslav People’s Army |
E544154
|
NE 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: Yugoslav People’s Army | Statement: [Cona B, militaryAdministration, Yugoslav People’s Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryAdministration Context triple: [Cona B, militaryAdministration, Yugoslav People’s Army]
-
A.
militarySystem
Indicates a relationship where an entity functions as, belongs to, or is characterized by a particular military organizational or operational system.
-
B.
militaryRelatedOffice
Indicates that an office, position, or role is associated with, derived from, or functionally connected to the military or armed forces.
-
C.
militarySection
Indicates that one entity is a specific branch, division, or section within a larger military organization or force.
-
D.
militaryControl
chosen
Indicates that one entity exercises authoritative military power, command, or occupation over another entity or territory.
-
E.
militaryDirector
Indicates that one entity serves as the military director or chief military authority for another entity.
- F. None of above.
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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a12c5871904819096b81af73e26a31b |
completed | May 24, 2026, 9:31 a.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 6:16 a.m.