Triple
T38059322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newcastle Airport Metro station |
E950296
|
entity |
| Predicate | hasAutomaticAnnouncements |
P131898
|
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: [Newcastle Airport Metro station, hasAutomaticAnnouncements, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAutomaticAnnouncements Context triple: [Newcastle Airport Metro station, hasAutomaticAnnouncements, yes]
-
A.
hasAnnouncementsSystem
Indicates that an entity is equipped with or uses a system for creating, managing, and delivering announcements.
-
B.
hasAutomaticTrainAnnouncements
chosen
Indicates that a transportation system or vehicle provides automated audio or visual announcements about train operations or stops.
-
C.
hasAnnouncement
Indicates that an entity issues, contains, or is associated with a specific announcement.
-
D.
hasPartyAnnouncements
Indicates that there exist announcements or notifications associated with a particular party or event.
-
E.
hasAnnouncers
Indicates that one entity serves as the announcer or commentary provider for another entity, such as an event, program, or broadcast.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: May 3, 2026, 4:21 p.m.