Triple
T33131624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hailun Road |
E847886
|
entity |
| Predicate | hasSafetyPlatformScreenDoors |
P22114
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hailun Road, hasSafetyPlatformScreenDoors, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSafetyPlatformScreenDoors Context triple: [Hailun Road, hasSafetyPlatformScreenDoors, yes]
-
A.
hasPlatformScreenDoors
chosen
Indicates that a transit station or platform is equipped with platform screen doors separating passengers from the tracks.
-
B.
hasDoorGuard
Indicates that an entity has another entity serving as a guard for its door or entrance.
-
C.
doorSafety
Indicates that a door meets specified safety conditions or standards, such as being secure, unobstructed, and compliant with safety regulations.
-
D.
designedForPlatformEdgeDoorsCompatibility
Indicates that something is intended or configured to be compatible with platform edge doors.
-
E.
hasEndDoors
Indicates that an object or structure is equipped with doors located at one or more of its ends.
- 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 1, 2026, 1:27 a.m.