Triple
T14621607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akko railway station |
E343234
|
entity |
| Predicate | hasElectronicDepartureBoards |
P69511
|
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: [Akko railway station, hasElectronicDepartureBoards, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectronicDepartureBoards Context triple: [Akko railway station, hasElectronicDepartureBoards, yes]
-
A.
usedOnDepartureBoards
Indicates that something (such as a name, code, or label) is the form that is shown on departure boards to represent a service or destination.
-
B.
hasDepartureScreens
chosen
Indicates that a location or facility is equipped with screens displaying departure information for services such as trains, buses, or flights.
-
C.
endStationProvidesAccessTo
Indicates that a particular end station offers access or connectivity to another location, service, or network resource.
-
D.
hasRailPlatforms
Indicates that an entity is equipped with one or more rail platforms used for boarding or alighting from trains.
-
E.
hasElectronicTicketing
Indicates that an entity supports or provides electronic ticketing for access, booking, or transactions.
- 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_69d822dffc3c8190aa173b90761bffda |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb466a61c81908a110d40fb959b6f |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.