Triple
T18273576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Very High Readiness Joint Task Force |
E437674
|
entity |
| Predicate | responseTime |
P55905
|
FINISHED |
| Object | a few days |
—
|
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: a few days | Statement: [Very High Readiness Joint Task Force, responseTime, a few days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responseTime Context triple: [Very High Readiness Joint Task Force, responseTime, a few days]
-
A.
intendedResponseTime
chosen
Indicates the expected or planned amount of time within which a response should be given or received.
-
B.
resolutionTime
Indicates the duration taken to resolve an issue, task, or request from its initiation to its completion.
-
C.
performanceTime
Indicates the specific time or time interval at which a performance or event takes place.
-
D.
responseExpected
Indicates that a reply, action, or follow-up is anticipated from a specified party in relation to a prior communication or event.
-
E.
deliverySpeed
Indicates the rate or promptness with which an item, service, or information is delivered from a source to a recipient.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5005006108190bbddddbe6bbdc911 |
completed | April 19, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.