Triple
T28366028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MBTA bus route CT3 |
E718489
|
entity |
| Predicate | connectsTypeOfHub |
P193707
|
FINISHED |
| Object | medical hub |
—
|
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: medical hub | Statement: [MBTA bus route CT3, connectsTypeOfHub, medical hub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsTypeOfHub Context triple: [MBTA bus route CT3, connectsTypeOfHub, medical hub]
-
A.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
B.
connectsDeviceType
Indicates a relationship where one entity is associated with or linked to a specific type or category of device.
-
C.
connectsMajorHub
Indicates that one entity serves as a link or route between major hubs or primary nodes in a network.
-
D.
connectorTypeDesignation
Indicates the specific type or classification assigned to a connector within a connection or interface relationship.
-
E.
connectsServiceType
Indicates a relationship where one entity is linked or associated to another based on a specific type of service connection.
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
| PDg | Predicate description generation | batch_69fd509cdc5c8190a5f2c451bc0d0b25 |
completed | May 8, 2026, 2:55 a.m. |
Created at: April 28, 2026, 12:55 a.m.