Triple
T23648940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Shrovetide Football |
E584115
|
entity |
| Predicate | startTimeEachDay |
P62290
|
FINISHED |
| Object | 14:00 |
—
|
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: 14:00 | Statement: [Royal Shrovetide Football, startTimeEachDay, 14:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeEachDay Context triple: [Royal Shrovetide Football, startTimeEachDay, 14:00]
-
A.
startTimeDetail
Indicates the specific, often more granular or formatted, time at which an event or action begins.
-
B.
startTime_ma
Indicates the time at which an event, action, or relationship begins, measured in millions of years ago (Ma).
-
C.
endTimeDetail
Indicates the specific or refined information about when an event, action, or state concludes.
-
D.
startsOnDay
Indicates that an event or process begins on a specified calendar day.
-
E.
startTimeAsCardinal
chosen
Indicates the specific clock time at which an event or action begins, expressed as a cardinal (numeric) value rather than a textual or formatted time.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b287606881909926de5efd882a76 |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:49 p.m.