Triple
T17163766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bénouville Bridge |
E416551
|
entity |
| Predicate | captureTime |
P11258
|
FINISHED |
| Object | shortly after midnight |
—
|
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: shortly after midnight | Statement: [Bénouville Bridge, captureTime, shortly after midnight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captureTime Context triple: [Bénouville Bridge, captureTime, shortly after midnight]
-
A.
capturedAt
chosen
Indicates the specific time or moment at which an entity was captured, recorded, or taken.
-
B.
timeRecorded
Indicates that a specific point or period in time has been captured and stored as associated with an event, action, or state.
-
C.
capturedDuring
Indicates that one event or state occurred within the temporal span of another, typically representing that something was recorded, seized, or documented while a specific situation or activity was taking place.
-
D.
hasCaptureDate
Indicates the date on which something (such as an image, video, or data sample) was originally captured or recorded.
-
E.
captures
Indicates that one entity seizes, traps, or takes control of another entity, often preventing its escape or freedom.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f913c84481908bb5da8bcc6a2e62 |
completed | April 18, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.