Triple
T30817095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chef-du-Pont |
E784809
|
entity |
| Predicate | eventOccurredNearby |
P45864
|
FINISHED |
| Object | airborne operations on 6 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: airborne operations on 6 June 1944 | Statement: [Chef-du-Pont, eventOccurredNearby, airborne operations on 6 June 1944]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventOccurredNearby Context triple: [Chef-du-Pont, eventOccurredNearby, airborne operations on 6 June 1944]
-
A.
nearbyEvent
Indicates that one event occurs close in space or time to another event.
-
B.
hasNearbyEvent
chosen
Indicates that an event occurs close in space or time to the referenced entity.
-
C.
hasNearbyEventType
Indicates that an event of a specified type occurs in close spatial or contextual proximity to a given reference entity or location.
-
D.
occursNear
Indicates that one event or entity takes place or exists in close spatial proximity to another.
-
E.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 29, 2026, 8:44 p.m.