Triple
T19363996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dundee derby |
E484352
|
entity |
| Predicate | occursInTime |
P3824
|
FINISHED |
| Object | football season schedule |
—
|
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: football season schedule | Statement: [Dundee derby, occursInTime, football season schedule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursInTime Context triple: [Dundee derby, occursInTime, football season schedule]
-
A.
occurredDuring
chosen
Indicates that one event or action took place within the temporal span of another event or time period.
-
B.
meetsInTimePeriod
Indicates that two entities encounter or come together during a specified time period.
-
C.
appearsInTimePeriod
Indicates that an entity is present, active, or occurs within a specified time period.
-
D.
occurredIn
Indicates that an event or action took place within a specific location, context, or time frame.
-
E.
occursAt
Indicates that an event or action takes place at a specific time or location.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e619a9ac68819082cf9deadf526156 |
completed | April 20, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:34 p.m.