Triple
T7693267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayeux-Calvados Award for War Correspondents |
E174301
|
entity |
| Predicate | typicalTimeHeld |
P47280
|
FINISHED |
| Object | October |
—
|
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: October | Statement: [Bayeux-Calvados Award for War Correspondents, typicalTimeHeld, October]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTimeHeld Context triple: [Bayeux-Calvados Award for War Correspondents, typicalTimeHeld, October]
-
A.
usualMonthHeld
chosen
Indicates the month in which an event or activity is typically or customarily held.
-
B.
lastHeldIn
Indicates that an event or state most recently took place or was hosted in a particular location or context.
-
C.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
D.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
E.
recordHeldUntil
Indicates that a record remained valid, in force, or applicable up to a specified end time or condition.
- 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_69c6995966348190939e6c37ba272c06 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c706d1f0208190bc5b695aa5736244 |
completed | March 27, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69c70163dea88190ae729df50e63dfd7 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:02 p.m.