Triple
T1460031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaieties (Stanford student musical) |
E31489
|
entity |
| Predicate | traditionallyHeldDuring |
P3473
|
FINISHED |
| Object | Big Game week |
—
|
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: Big Game week | Statement: [Gaieties (Stanford student musical), traditionallyHeldDuring, Big Game week]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyHeldDuring Context triple: [Gaieties (Stanford student musical), traditionallyHeldDuring, Big Game week]
-
A.
celebratedDuring
chosen
Indicates that an event, tradition, or activity takes place or is observed within the time span of a specified celebration or festive period.
-
B.
typicallyHeldIn
Indicates that an event, activity, or process most commonly or usually takes place within a particular location, venue, or context.
-
C.
annualEvent
Indicates that an event occurs once every year on a recurring basis.
-
D.
seCelebraEn
Indicates that an event or occasion takes place or is held at a specific location or venue.
-
E.
celebratedEvent
Indicates that an entity has been honored, commemorated, or festively observed as a special event.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c59d6dd88190b8ff3bda90aef7e2 |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47ec5108190b1772237f2e5d90b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.