Triple
T10779075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine expeditionary brigade |
E254268
|
entity |
| Predicate | timeframeToDeploy |
P38735
|
FINISHED |
| Object | rapid deployment on order |
—
|
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: rapid deployment on order | Statement: [Marine expeditionary brigade, timeframeToDeploy, rapid deployment on order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeframeToDeploy Context triple: [Marine expeditionary brigade, timeframeToDeploy, rapid deployment on order]
-
A.
deploymentTime
Indicates the point in time at which something is deployed, initiated, or put into operation.
-
B.
redeploymentTime
Indicates the amount of time required to redeploy or reassign a resource, system, or unit from one operational state or location to another.
-
C.
deployedFor
Indicates that one entity is deployed or put into operational use to serve, support, or act on behalf of another entity.
-
D.
timeFrameSpecified
chosen
Indicates that a specific temporal period or duration has been explicitly defined or constrained for the related event, action, or relationship.
-
E.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732c25478819093dedec0c8556777 |
completed | April 9, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69d6f31455648190b5c24690487b1b54 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.