Triple
T3840265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Haye Sainte |
E93432
|
entity |
| Predicate | timeOfCapture |
P38643
|
FINISHED |
| Object | evening of 18 June 1815 |
—
|
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: evening of 18 June 1815 | Statement: [La Haye Sainte, timeOfCapture, evening of 18 June 1815]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfCapture Context triple: [La Haye Sainte, timeOfCapture, evening of 18 June 1815]
-
A.
capturedAt
Indicates the specific time or moment at which an entity was captured, recorded, or taken.
-
B.
hasCaptureDate
chosen
Indicates the date on which something (such as an image, video, or data sample) was originally captured or recorded.
-
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.
timeOfInitiation
Indicates the specific point in time at which an action, event, or process begins.
-
E.
capturedYear
Indicates the year in which an entity was captured or taken into custody.
- 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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeeba1535c8190b36e2ab2d4514b54 |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74dcecc819098285483ec721b40 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.