Triple
T1389652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teatro Romano di Trieste |
E29924
|
entity |
| Predicate | languageOfLocality |
P10892
|
FINISHED |
| Object | Italian |
—
|
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: Italian | Statement: [Teatro Romano di Trieste, languageOfLocality, Italian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfLocality Context triple: [Teatro Romano di Trieste, languageOfLocality, Italian]
-
A.
regionLanguage
chosen
Indicates that a particular language is used or officially recognized within a specific geographic region.
-
B.
majorityLanguageOf
Indicates that a given language is the primary or most widely spoken language within a specified group, region, or entity.
-
C.
locale
Indicates that one entity is the place, setting, or geographic area in which another entity exists, occurs, or is situated.
-
D.
standardLanguageOf
Indicates that one entity serves as the officially recognized or commonly used standard language for another entity (such as a country, region, or organization).
-
E.
macrolanguageOf
Indicates that one language functions as a macrolanguage encompassing or grouping together one or more related individual languages.
- 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c35ce48c81909aaad7dfa2df63fa |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4beffcf808190ab4cd0271257ce63 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.