Triple
T36750653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sapporo Municipal Subway 5000 series |
E907901
|
entity |
| Predicate | hasOnboardAnnouncements |
P74699
|
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: [Sapporo Municipal Subway 5000 series, hasOnboardAnnouncements, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnboardAnnouncements Context triple: [Sapporo Municipal Subway 5000 series, hasOnboardAnnouncements, yes]
-
A.
hasAnnouncement
Indicates that an entity issues, contains, or is associated with a specific announcement.
-
B.
hasAnnouncementsSystem
chosen
Indicates that an entity is equipped with or uses a system for creating, managing, and delivering announcements.
-
C.
hasOnboardFeature
Indicates that an entity includes or is equipped with a particular feature as part of its built-in or onboard capabilities.
-
D.
hasOnboardButton
Indicates that one entity is equipped with or includes a button installed on or within it.
-
E.
hasOnboardFunction
Indicates that an entity includes or supports a particular function internally as part of its built-in capabilities.
- 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_69f76e76d10881909ec1679bc043108c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 3, 2026, 4:12 p.m.