Triple
T12955239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Active Component |
E309993
|
entity |
| Predicate | hasReadinessRequirement |
P107681
|
FINISHED |
| Object | maintain deployable status |
—
|
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: maintain deployable status | Statement: [Active Component, hasReadinessRequirement, maintain deployable status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReadinessRequirement Context triple: [Active Component, hasReadinessRequirement, maintain deployable status]
-
A.
hasEntryRequirement
Indicates that one entity specifies conditions or qualifications that must be met before another entity is allowed access, participation, or admission.
-
B.
hasQueueRequirement
Indicates that an entity must satisfy or adhere to a specified queue-related condition or rule.
-
C.
hasObservationRequirement
Indicates that one entity imposes or specifies an observation-related condition or requirement that must be satisfied by another entity or process.
-
D.
establishedRequirement
Indicates that one entity has formally set or defined a requirement that another entity is expected to satisfy or comply with.
-
E.
requiresDataAvailability
Indicates that one entity’s operation, validity, or execution is contingent on the presence, accessibility, or readiness of specific data.
- 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_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. |
| PDg | Predicate description generation | batch_69d97e5811f481908178fac6d2e0efcd |
completed | April 10, 2026, 10:48 p.m. |
Created at: April 9, 2026, 5:44 p.m.