Triple
T24567202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Douve River |
E607823
|
entity |
| Predicate | nearbyOperation |
P98897
|
FINISHED |
| Object | Operation Overlord |
—
|
NE NERFINISHED |
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: Operation Overlord | Statement: [Douve River, nearbyOperation, Operation Overlord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyOperation Context triple: [Douve River, nearbyOperation, Operation Overlord]
-
A.
nearbyActivity
Indicates that an activity occurs close in space or proximity to a specified entity or location.
-
B.
nearbyUse
Indicates that one entity uses or operates another entity that is located nearby or in close physical proximity.
-
C.
nearbyEvent
Indicates that one event occurs close in space or time to another event.
-
D.
nearbyCurrent
Indicates that one entity is located close to another entity at the present moment or in the current context.
-
E.
hasNearbyOperations
chosen
Indicates that an entity conducts operations or activities in locations that are geographically close to a specified reference point or area.
- 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a92141f88190bcbd7c6aeafc0725 |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:28 a.m.