Triple
T145861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CharlieCard |
E3327
|
entity |
| Predicate | distributionPoint |
P1486
|
FINISHED |
| Object | MBTA subway stations |
—
|
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: MBTA subway stations | Statement: [CharlieCard, distributionPoint, MBTA subway stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distributionPoint Context triple: [CharlieCard, distributionPoint, MBTA subway stations]
-
A.
distribution
Indicates the act or pattern of giving, delivering, or spreading something from one source to multiple recipients or locations.
-
B.
distributionMethod
chosen
Indicates the means or channel through which something (such as a product, resource, or information) is delivered or made available to recipients.
-
C.
distributor
Indicates that an entity is responsible for supplying, delivering, or making another entity’s products or materials available to others.
-
D.
endPoint
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
-
E.
primaryStation
Indicates that one station is designated as the main or principal station associated with another entity or within a given context.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a257ea7eac8190884a53453a9e0dd6 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a25656a4fc81908a87678ac3d28f93 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.