Triple
T10940606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regent’s Park station |
E258459
|
entity |
| Predicate | hasPlatformsConfiguration |
P842
|
FINISHED |
| Object | 2 side 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: 2 side platforms | Statement: [Regent’s Park station, hasPlatformsConfiguration, 2 side platforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlatformsConfiguration Context triple: [Regent’s Park station, hasPlatformsConfiguration, 2 side platforms]
-
A.
hasNumberOfPlatforms
Indicates the relationship that specifies how many platforms are associated with a given entity.
-
B.
hasPlatformType
chosen
Indicates that an entity is associated with or characterized by a specific type or category of platform.
-
C.
hasTargetPlatform
Indicates that something is intended to run on, be compatible with, or be deployed to a specified platform.
-
D.
hasPlatformsConnectedBy
Indicates that two or more platforms are linked together by some connecting structure or mechanism.
-
E.
hasDeepPlatform
Indicates that one entity possesses or provides a platform characterized by significant depth, capability, or extensiveness in supporting another entity’s activities or functions.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770c2821c8190a7b08276c4bfbf33 |
completed | April 9, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69d72e816a98819096d6c10dfb88a66a |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.