Triple
T25277109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ready Reserve Force vessel |
E633730
|
entity |
| Predicate | canBeActivatedWithin |
P161640
|
FINISHED |
| Object | 5 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: 5 days | Statement: [Ready Reserve Force vessel, canBeActivatedWithin, 5 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeActivatedWithin Context triple: [Ready Reserve Force vessel, canBeActivatedWithin, 5 days]
-
A.
canBeActivatedFor
Indicates that one entity is capable of being put into an active or operational state by or for another entity.
-
B.
isPotentiallyActive
Indicates that an entity has the capacity or conditions to become active, but is not necessarily active at the present moment.
-
C.
activatedFor
Indicates that something has been enabled, triggered, or made operational specifically on behalf of or in the context of a particular entity or target.
-
D.
canBeUsed
Indicates that one entity is suitable or available to serve a particular function, purpose, or role in relation to another entity or context.
-
E.
activeAt
Indicates that an entity is functioning, valid, or in effect during a specified time or at a particular location or context.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6200ac60481909895c61d050b1338 |
completed | May 2, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61f109ef48190873bfe18638d2046 |
completed | May 2, 2026, 3:58 p.m. |
Created at: April 21, 2026, 1:18 p.m.