Triple
T5331067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liberation Day (Bevrijdingsdag) |
E123308
|
entity |
| Predicate | followsDate |
P43308
|
FINISHED |
| Object | May 4 |
—
|
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: May 4 | Statement: [Liberation Day (Bevrijdingsdag), followsDate, May 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsDate Context triple: [Liberation Day (Bevrijdingsdag), followsDate, May 4]
-
A.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
-
B.
followsApproximately
Indicates that one entity follows another in sequence or order, but with some allowable deviation or inexactness in timing, position, or pattern.
-
C.
followedIn
Indicates that one entity began following or subscribing to another entity, typically in a social or sequential context.
-
D.
followsTime
chosen
Indicates that one event, state, or time period occurs after and in temporal succession to another.
-
E.
follows
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
- 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_69bd46477f9081909d242a327d749466 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85969cc88190a3a5efbab7d9fe86 |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2 p.m.