Triple
T34385495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Theatre Street |
E882544
|
entity |
| Predicate | toponymLanguageVariant |
P24399
|
FINISHED |
| Object | Maltese |
—
|
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: Maltese | Statement: [Old Theatre Street, toponymLanguageVariant, Maltese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toponymLanguageVariant Context triple: [Old Theatre Street, toponymLanguageVariant, Maltese]
-
A.
hasLanguageOfToponym
chosen
Indicates that a place name (toponym) is expressed in or associated with a particular language.
-
B.
toponymsMayDifferInScript
Indicates that two toponyms refer to the same place but are written using different writing systems or scripts.
-
C.
isVariantOfToponym
Indicates that one toponym is an alternative or variant form (e.g., spelling, language, or historical version) of another place name.
-
D.
toponymsMayDifferInPronunciation
Indicates that two toponyms (place names) may have different spoken pronunciations even if they are otherwise related or similar.
-
E.
toponymsShareSpelling
Indicates that two place names share the same or very similar written form or spelling.
- 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_69f349c0219881909393bbbc1edc8161 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.