Triple
T13814153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Studio 1A |
E331970
|
entity |
| Predicate | usedForSpecialEvents |
P37420
|
FINISHED |
| Object | Today show concerts |
—
|
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: Today show concerts | Statement: [Studio 1A, usedForSpecialEvents, Today show concerts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForSpecialEvents Context triple: [Studio 1A, usedForSpecialEvents, Today show concerts]
-
A.
specialOccasion
Indicates that an event or situation is associated with a notable or exceptional occasion, such as a celebration, milestone, or culturally significant date.
-
B.
specialtyEvent
chosen
Indicates that an event is designated as a special or distinctive occurrence, often differing from regular or routine events in nature or purpose.
-
C.
usedOnOccasions
Indicates that something is employed or utilized during specific events, times, or circumstances rather than continuously.
-
D.
servingOccasion
Indicates the occasion, event, or context during which something (typically food or drink) is served.
-
E.
premiereOccasion
Indicates the event or context in which something (such as a work, show, or product) is first publicly presented or launched.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de027198f8819095da3e714ac241f5 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc862e9608190bd8a3d883959b7e4 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:12 p.m.