Triple
T4349491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Oaks |
E97985
|
entity |
| Predicate | typicalScheduling |
P3309
|
FINISHED |
| Object | day one of the Derby Festival |
—
|
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: day one of the Derby Festival | Statement: [The Oaks, typicalScheduling, day one of the Derby Festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalScheduling Context triple: [The Oaks, typicalScheduling, day one of the Derby Festival]
-
A.
typicalSchedule
chosen
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
-
B.
typicalTimes
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
-
C.
schedulingRule
Indicates a rule or constraint that governs when, how, or under what conditions an event or task may be scheduled.
-
D.
typicalAppointment
Indicates that an appointment represents a standard, usual, or commonly occurring scheduling arrangement between entities.
-
E.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
- 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_69b3454965f881908c41190bb22f0e4b |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351a6e89c8190b9bf2cccb63839b3 |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f51ed7c8190b7bf5f44b56b730d |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:15 p.m.