Triple
T596347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Davis station |
E17390
|
entity |
| Predicate | hasElectronicSignage |
P5950
|
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: [Davis station, hasElectronicSignage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectronicSignage Context triple: [Davis station, hasElectronicSignage, yes]
-
A.
hasSignage
chosen
Indicates that appropriate signs or visual markers are present to convey information, directions, warnings, or identification related to the associated entity.
-
B.
hasDigitalAccess
Indicates that an entity has the ability or permission to use or access digital resources, services, or information.
-
C.
hasSign
Indicates that an entity possesses, displays, or is associated with a particular sign or symbol.
-
D.
hasDigitalService
Indicates that an entity provides, offers, or is associated with a service delivered through digital or online means.
-
E.
hasExhibitFormat
Indicates the specific format or medium in which an exhibit is presented or made available.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bd3e5e08190be95cb2009aad42d |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cfb52c81908d816a4c5579c321 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.