Triple
T1432334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Ready Reserve Force |
E30475
|
entity |
| Predicate | activationTime |
P28440
|
FINISHED |
| Object | usually within 5 to 10 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: usually within 5 to 10 days | Statement: [United States Ready Reserve Force, activationTime, usually within 5 to 10 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activationTime Context triple: [United States Ready Reserve Force, activationTime, usually within 5 to 10 days]
-
A.
activeFrom
Indicates the starting point in time from which an entity or relationship is considered active or in effect.
-
B.
reactivatedDuring
Indicates that an entity becomes active again within the time span or context defined by another event or condition.
-
C.
deploymentTime
Indicates the point in time at which something is deployed, initiated, or put into operation.
-
D.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
E.
activityTime
Indicates the time period during which an activity occurs or is scheduled to take place.
- 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_69a498fc69ec8190b61722bd4b67c4d2 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c500a9888190a16fbb1ec97a79c9 |
completed | March 1, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69a4c4771c9481908ae47c959debbe77 |
completed | March 1, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69a4c4feea448190b2b5071b28a5b608 |
completed | March 1, 2026, 11 p.m. |
Created at: March 1, 2026, 8 p.m.