Triple
T1829320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EU Battlegroups |
E40724
|
entity |
| Predicate | deploymentReadinessTime |
P17474
|
FINISHED |
| Object | 10 days from EU decision |
—
|
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: 10 days from EU decision | Statement: [EU Battlegroups, deploymentReadinessTime, 10 days from EU decision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deploymentReadinessTime Context triple: [EU Battlegroups, deploymentReadinessTime, 10 days from EU decision]
-
A.
deploymentTime
Indicates the point in time at which something is deployed, initiated, or put into operation.
-
B.
activationTime
Indicates the specific point in time at which an entity, process, or function becomes active or starts operating.
-
C.
timeToComplete
chosen
Indicates the duration required for an entity or process to be fully completed.
-
D.
declaredFullyOperationalBy
Indicates that one entity has officially stated that another entity is completely ready and capable of functioning as intended.
-
E.
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.
- 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_69a8864644bc8190b2358ab897194ac1 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb45402688190b9a535b14030c354 |
completed | March 7, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69abafd6a9948190ac2b2743db6f8f69 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:32 p.m.