Triple
T7337555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bura |
E169166
|
entity |
| Predicate | localNameInLanguage |
P29131
|
FINISHED |
| Object | Bura in Croatian |
—
|
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: Bura in Croatian | Statement: [Bura, localNameInLanguage, Bura in Croatian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localNameInLanguage Context triple: [Bura, localNameInLanguage, Bura in Croatian]
-
A.
localLanguageName
Indicates the name of a language as it is written or referred to in its own local or native form.
-
B.
hasNameInLocalLanguage
Indicates that an entity is associated with a name expressed in the local or native language of a given context or region.
-
C.
languageOfWorkOrName
Indicates the language in which a work is created or a name is expressed.
-
D.
alternateLanguageName
Indicates that an entity has an additional name or label in a different language from its primary or default name.
-
E.
localNameInCroatian
chosen
Indicates that the specified name is the local or native name of an entity when expressed in the Croatian language.
- 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_69c68a568a6481908f11e20db7bc8446 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f347f25081908e6086d4073295f5 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f028fd748190b2ea5c3081958a42 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:04 p.m.