Triple
T8680477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AKT |
E206022
|
entity |
| Predicate | isMilitaryOnly |
P84459
|
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: [AKT, isMilitaryOnly, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMilitaryOnly Context triple: [AKT, isMilitaryOnly, true]
-
A.
hasMilitaryType
Indicates that an entity is associated with or classified under a specific military category, role, or type.
-
B.
hasMilitarySecurity
Indicates that an entity provides, maintains, or is responsible for military protection or defense for another entity or area.
-
C.
isMilitaryPostType
Indicates that something is classified as a type or category of military post or installation.
-
D.
isMilitaryOfficer
Indicates that the subject holds an official position as an officer within a military organization.
-
E.
militaryBranchEligibility
Indicates that an entity meets the required conditions to serve in a specified branch of the military.
- 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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4ae6d19c8190be003f7901c0468d |
completed | March 31, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69cc4567b5c881908d9ec5dcfc783fac |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc4ae517108190a71a86349815f4ce |
completed | March 31, 2026, 10:29 p.m. |
Created at: March 30, 2026, 6:32 p.m.