Triple
T1909802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashton Moss tram stop |
E38081
|
entity |
| Predicate | hasVisualAnnouncements |
P31727
|
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: [Ashton Moss tram stop, hasVisualAnnouncements, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisualAnnouncements Context triple: [Ashton Moss tram stop, hasVisualAnnouncements, yes]
-
A.
announcedTo
Indicates that one entity formally communicated or made known some information, decision, or event to another specific entity.
-
B.
hasBroadcastFeature
chosen
Indicates that an entity includes or supports a broadcast-related capability or functionality.
-
C.
hasBells
Indicates that an entity possesses or is equipped with one or more bells.
-
D.
announcedThat
Indicates that one entity publicly communicated or declared a specific fact, decision, or piece of information about another entity or situation.
-
E.
hasLookout
Indicates that one entity serves as a lookout or watchful observer for another entity, monitoring for potential events, threats, or changes.
- 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_69a8862a26088190aae5243695aeefc0 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafeba3d88190afcce67483d8625b |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.