Triple
T12783829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Jupiter |
E305572
|
entity |
| Predicate | dateClaimedInDescription |
P106896
|
FINISHED |
| Object | July 1944 |
—
|
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: July 1944 | Statement: [Operation Jupiter, dateClaimedInDescription, July 1944]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateClaimedInDescription Context triple: [Operation Jupiter, dateClaimedInDescription, July 1944]
-
A.
dateGranted
Indicates the specific date on which a right, status, or permission was formally conferred or approved.
-
B.
timeframeClaimedForSingularity
Indicates that an entity asserts or specifies a particular period of time in which a technological or singularity event is expected to occur.
-
C.
dateReceived
Indicates the point in time when something (such as a message, item, or document) was received by a recipient.
-
D.
landingDate
Indicates the date on which an entity arrives at or touches down on a specified destination or surface.
-
E.
usedToClaim
Indicates that something is employed as evidence, justification, or support in making a particular claim.
- 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e5cb3c08190b8e1e22de8b96e17 |
completed | April 10, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:29 p.m.