Triple
T142288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Station |
E2878
|
entity |
| Predicate | servesVenue |
P6789
|
FINISHED |
| Object | Boston Celtics home games at TD Garden |
—
|
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: Boston Celtics home games at TD Garden | Statement: [North Station, servesVenue, Boston Celtics home games at TD Garden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesVenue Context triple: [North Station, servesVenue, Boston Celtics home games at TD Garden]
-
A.
servesField
Indicates that one entity performs a service or function specifically for, or in support of, a particular field, domain, or area of activity.
-
B.
servesAtThePleasureOf
Indicates that one entity holds a position or role that can be terminated at any time by another entity, typically at the discretion or will of that other entity.
-
C.
venue
Indicates the place or location where an event, activity, or interaction takes place.
-
D.
servesLine
Indicates that a transportation stop, station, or facility is on and provides service for a particular transit line.
-
E.
servesMode
Indicates that one entity provides or operates in a particular manner, method, or mode in relation to another entity or context.
- 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a2580ca15481909fa3e87d804a1b23 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a2565559ac81909e0c4e095a7dfa27 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2580b00988190868ee24c0289cf70 |
completed | Feb. 28, 2026, 2:50 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.