Triple
T10041651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archer Artillery System |
E205308
|
entity |
| Predicate | redeploymentTime |
P91790
|
FINISHED |
| Object | short out-of-action time |
—
|
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: short out-of-action time | Statement: [Archer Artillery System, redeploymentTime, short out-of-action time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redeploymentTime Context triple: [Archer Artillery System, redeploymentTime, short out-of-action time]
-
A.
deploymentTime
Indicates the point in time at which something is deployed, initiated, or put into operation.
-
B.
deployedFor
Indicates that one entity is deployed or put into operational use to serve, support, or act on behalf of another entity.
-
C.
rebuildPeriod
Indicates the time span during which something is reconstructed or restored after damage, failure, or decommissioning.
-
D.
deploymentEnd
Indicates the point in time or event at which a deployment process or deployment state comes to an end.
-
E.
displacementPeriod
Indicates the time interval over which an entity is moved or shifted from one position or state to another.
- 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcee48d8c8190af7c93b60f8ca7cb |
completed | April 2, 2026, 2:05 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:55 p.m.