Triple
T18471313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tartini Square |
E451306
|
entity |
| Predicate | hasAlternativeLanguageToponym |
P63334
|
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: [Tartini Square, hasAlternativeLanguageToponym, Italian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeLanguageToponym Context triple: [Tartini Square, hasAlternativeLanguageToponym, Italian]
-
A.
hasLanguageOfToponym
Indicates that a place name (toponym) is expressed in or associated with a particular language.
-
B.
alternateLanguageName
chosen
Indicates that an entity has an additional name or label in a different language from its primary or default name.
-
C.
hasToponymicDerivatives
Indicates that a name or term serves as the source from which related place-based or toponymic names are derived.
-
D.
hasToponymicForm
Indicates that one entity is a toponymic (place-name-based) form or variant derived from another entity.
-
E.
hasAlternativeFamilyName
Indicates that an entity is associated with an additional or variant family name besides its primary family name.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5305f428c81909980bd30d150e7dd |
completed | April 19, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:34 a.m.