Triple
T248478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CTA Red Line Sox–35th station |
E5088
|
entity |
| Predicate | eventUse |
P8777
|
FINISHED |
| Object | stadium event crowds |
—
|
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: stadium event crowds | Statement: [CTA Red Line Sox–35th station, eventUse, stadium event crowds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventUse Context triple: [CTA Red Line Sox–35th station, eventUse, stadium event crowds]
-
A.
event
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
-
B.
eventRole
Indicates the specific function, capacity, or part an entity plays within an event or occurrence.
-
C.
featuresEvent
Indicates that an entity includes, presents, or highlights a particular event as part of its content or offering.
-
D.
hostsEvent
Indicates that an entity organizes and provides the venue or setting for an event to take place.
-
E.
eveCelebrationOn
Indicates that an event or entity is engaged in or associated with a celebration occurring on a specific date or occasion.
- F. None of above. chosen
Provenance (4 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d154ebc819087a5c9dc4f62ff44 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b64ea3081908de626a0e1445bdb |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c2ca46c81908c61696f31e59a98 |
completed | Feb. 28, 2026, 3:08 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.