Triple
T9829822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KNZY |
E238753
|
entity |
| Predicate | hasMilitaryRestriction |
P84459
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [KNZY, hasMilitaryRestriction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMilitaryRestriction Context triple: [KNZY, hasMilitaryRestriction, yes]
-
A.
isMilitaryOnly
chosen
Indicates that something is restricted exclusively to military use or participation, excluding civilians or non-military entities.
-
B.
hasMilitarySecurity
Indicates that an entity provides, maintains, or is responsible for military protection or defense for another entity or area.
-
C.
hasMilitaryType
Indicates that an entity is associated with or classified under a specific military category, role, or type.
-
D.
hasMilitaryStatus
Indicates that an entity possesses a specific military affiliation, role, or status (such as active duty, reserve, or veteran).
-
E.
hasMilitaryAuthority
Indicates that one entity possesses formal power or command to direct, control, or make decisions over the military activities or forces of another entity.
- 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_69ca84e0dd1881909800765d1e21f735 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3282a2481908913addf2b3fa58b |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:32 p.m.