Triple
T1475680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camden Yards station |
E30834
|
entity |
| Predicate | servesEventType |
P29202
|
FINISHED |
| Object | Major League Baseball games |
—
|
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: Major League Baseball games | Statement: [Camden Yards station, servesEventType, Major League Baseball games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesEventType Context triple: [Camden Yards station, servesEventType, Major League Baseball games]
-
A.
servesVenue
Indicates that an entity provides services or functions in support of a particular venue.
-
B.
servingOccasion
Indicates the occasion, event, or context during which something (typically food or drink) is served.
-
C.
servesSport
Indicates that one entity provides or is used for playing, supporting, or accommodating a particular sport.
-
D.
alsoHostedEventType
Indicates that the same host was responsible for organizing or holding another event of a specified type.
-
E.
canServeIn
Indicates that one entity is eligible, authorized, or suitable to perform a role, function, or duty within another entity, context, or organization.
- 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_69a498fe55a88190ab7f9e40ace88e49 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c602387c8190b97a20c8e05e3d16 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c484e52c81908948ff8c0a42751b |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c57984088190b2c2d2d9cc2e5df9 |
completed | March 1, 2026, 11:02 p.m. |
Created at: March 1, 2026, 8:11 p.m.