Triple
T12955140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Active Component |
E309991
|
entity |
| Predicate | readinessRequirement |
P11883
|
FINISHED |
| Object | high readiness |
—
|
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: high readiness | Statement: [Army Active Component, readinessRequirement, high readiness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readinessRequirement Context triple: [Army Active Component, readinessRequirement, high readiness]
-
A.
establishedRequirement
Indicates that one entity has formally set or defined a requirement that another entity is expected to satisfy or comply with.
-
B.
readinessCategory
chosen
Indicates the classification of an entity based on its current level or state of preparedness for a given purpose or activity.
-
C.
preparationRequirement
Indicates that one entity must be prepared, configured, or made ready as a necessary condition before another entity, action, or process can occur or be valid.
-
D.
requiresDataAvailability
Indicates that one entity’s operation, validity, or execution is contingent on the presence, accessibility, or readiness of specific data.
-
E.
evaluationRequirement
Indicates that one entity imposes or specifies conditions under which another entity must be assessed, tested, or evaluated.
- 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97dba57988190b786ffed55687a72 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:44 p.m.