Triple
T25617396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st BCT |
E642194
|
entity |
| Predicate | deploymentReadiness |
P49856
|
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: [1st BCT, deploymentReadiness, high readiness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deploymentReadiness Context triple: [1st BCT, deploymentReadiness, high readiness]
-
A.
deploymentCondition
Indicates the specific requirements or circumstances under which something may be deployed or put into operation.
-
B.
operationalReadiness
chosen
Indicates that an entity is in a state where it is fully prepared, equipped, and able to perform its intended function or mission.
-
C.
deploymentCapability
Indicates the ability or capacity of an entity to deploy, release, or roll out another entity (such as a system, service, or resource) into an operational environment.
-
D.
deploymentRequires
Indicates that performing a particular deployment is contingent upon the prior existence, completion, or availability of another specified resource, condition, or action.
-
E.
deploymentTime
Indicates the point in time at which something is deployed, initiated, or put into operation.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5f9e8734c8190a214685b1647abe1 |
completed | May 2, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5:01 p.m.