Triple
T3580695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3rd Battalion, Parachute Regiment |
E75790
|
entity |
| Predicate | operationalReadiness |
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: [3rd Battalion, Parachute Regiment, operationalReadiness, high-readiness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalReadiness Context triple: [3rd Battalion, Parachute Regiment, operationalReadiness, high-readiness]
-
A.
fullyOperationalBy
Indicates that an entity is expected or required to be completely functional and ready for use no later than a specified time or event.
-
B.
operationalRequirement
Indicates that one entity specifies a condition or capability that must be met for another entity to function or operate as intended.
-
C.
becameOperational
Indicates that an entity transitioned from a non-functioning or inactive state to an active, functioning, or service-ready state at a certain point in time.
-
D.
declaredFullyOperationalBy
Indicates that one entity has officially stated that another entity is completely ready and capable of functioning as intended.
-
E.
isProductionReady
Indicates that something has met all necessary quality, stability, and performance criteria to be safely deployed and used in a live production environment.
- 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_69ad85d6dc3c8190b491b79b83e25461 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc101738c81908d38987f8fa291ef |
completed | March 8, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69adb83810c481909c645c08b978edc1 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb8e4ba948190a9b777cf7f788b96 |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:21 p.m.