Triple
T7622557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitchburg Line stations |
E172534
|
entity |
| Predicate | havePlatformType |
P842
|
FINISHED |
| Object | low-level platforms |
—
|
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: low-level platforms | Statement: [Fitchburg Line stations, havePlatformType, low-level platforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: havePlatformType Context triple: [Fitchburg Line stations, havePlatformType, low-level platforms]
-
A.
hasPlatformType
chosen
Indicates that an entity is associated with or characterized by a specific type or category of platform.
-
B.
hasPrimaryPlatform
Indicates that one entity is designated as the main or principal platform associated with another entity.
-
C.
hasTargetPlatform
Indicates that something is intended to run on, be compatible with, or be deployed to a specified platform.
-
D.
supportedPlatform
Indicates that one entity (such as a system, application, or service) is compatible with and can operate on a particular platform.
-
E.
consideredPlatform
Indicates that one entity is regarded or treated as a platform (e.g., a base, medium, or environment) for another entity or activity.
- 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_69c699506b308190826894dab1d9ea86 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fe73ff7c8190ab1218d97b37416d |
completed | March 27, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e725a88190b1f05dd224f7f4f2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:56 p.m.