Triple
T30260771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dahuasan Road station |
E769483
|
entity |
| Predicate | hasEnglishSignage |
P183503
|
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: [Dahuasan Road station, hasEnglishSignage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnglishSignage Context triple: [Dahuasan Road station, hasEnglishSignage, yes]
-
A.
hasIrishLanguageSignage
Indicates that signage associated with an entity includes text in the Irish language.
-
B.
officialLanguageOfSignage
Indicates that a particular language is the one officially used on public signs and signage within a given place or context.
-
C.
hasTouristSignage
Indicates that there is official signage present to guide or inform tourists about a place, route, or attraction.
-
D.
hasSignageIn
Indicates that appropriate signs or signage for an entity are present or installed within a specified location or area.
-
E.
hasSignage
Indicates that appropriate signs or visual markers are present to convey information, directions, warnings, or identification related to the associated entity.
- F. None of above. chosen
Provenance (4 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_69f22484a5f48190b678cd607700bc82 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7a01efcc08190bba489a9099b8684 |
completed | May 3, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79f477c4c8190a35cb6d87b1dcbd1 |
completed | May 3, 2026, 7:17 p.m. |
Created at: April 29, 2026, 7:41 p.m.