Triple
T14156960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper House Hall |
E350836
|
entity |
| Predicate | tourLanguageAvailability |
P48682
|
FINISHED |
| Object | multiple languages |
—
|
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: multiple languages | Statement: [Upper House Hall, tourLanguageAvailability, multiple languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourLanguageAvailability Context triple: [Upper House Hall, tourLanguageAvailability, multiple languages]
-
A.
languagesSpoken
Indicates that an entity is able to communicate using one or more specified languages.
-
B.
languageUsedInTourism
chosen
Indicates that a particular language is used for communication and services within tourism activities or contexts.
-
C.
includesLanguagesSpokenAlong
Indicates that something (such as a region, route, or area) encompasses or contains the set of languages spoken along its extent or within its boundaries.
-
D.
tourOpened
Indicates that a tour has begun or been made available for participation or viewing.
-
E.
hasPrimaryLanguageNearby
Indicates that an entity is associated with a primary language that is predominantly used or present in its immediate geographic or contextual vicinity.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6135744c81909a43d659f5fe2895 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:58 a.m.