Triple
T4236248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VII Corps |
E94699
|
entity |
| Predicate | operationStartContext |
P24545
|
FINISHED |
| Object | D-Day landings in June 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: D-Day landings in June 1944 | Statement: [VII Corps, operationStartContext, D-Day landings in June 1944]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationStartContext Context triple: [VII Corps, operationStartContext, D-Day landings in June 1944]
-
A.
operationStart
Indicates the point in time or event at which a specific operation or process begins.
-
B.
activityStartContext
chosen
Indicates the circumstances, conditions, or situation present at the moment an activity begins.
-
C.
notableOfficeStartContext
Indicates the contextual circumstances or conditions (such as time, place, or situation) surrounding the beginning of a notable office or position held by an entity.
-
D.
instructionBegan
Indicates that an instructional process or teaching activity has started.
-
E.
operateIn
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
- 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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e7422a88190955f5f4347fa80d2 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f3bd188190b0cd613e8a5c1683 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.