Triple
T14579471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capodistria |
E342148
|
entity |
| Predicate | usedAsToponymIn |
P20238
|
FINISHED |
| Object | Italian historical documents |
—
|
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 historical documents | Statement: [Capodistria, usedAsToponymIn, Italian historical documents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsToponymIn Context triple: [Capodistria, usedAsToponymIn, Italian historical documents]
-
A.
usedAsTownNameFor
Indicates that something serves as the official or common name of a particular town.
-
B.
hasToponymicUse
chosen
Indicates that a term or name is used as a toponym, i.e., as a place name or geographic designation.
-
C.
hasNotableToponym
Indicates that an entity is associated with a place name that is particularly notable, distinctive, or significant.
-
D.
toponymRefersTo
Indicates that a place name (toponym) designates or refers to a specific geographic entity or location.
-
E.
hasPlaceNamesakeIn
Indicates that something is named after a particular place or location.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb3f6f78c81908a30ecb4c025299d |
completed | April 14, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:24 a.m.