Triple
T34626448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hakone Ropeway |
E889149
|
entity |
| Predicate | hasMultilingualSignage |
P183503
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Hakone Ropeway, hasMultilingualSignage, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultilingualSignage Context triple: [Hakone Ropeway, hasMultilingualSignage, English]
-
A.
hasEnglishSignage
chosen
Indicates that the subject features signs or written information presented in the English language.
-
B.
hasIrishLanguageSignage
Indicates that signage associated with an entity includes text in the Irish language.
-
C.
officialLanguageOfSignage
Indicates that a particular language is the one officially used on public signs and signage within a given place or context.
-
D.
hasAdditionalLanguageOfSignage
Indicates that an entity has signage presented in one or more additional languages beyond the primary language used.
-
E.
hasTouristSignage
Indicates that there is official signage present to guide or inform tourists about a place, route, or attraction.
- 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: May 1, 2026, 2:04 a.m.