Triple
T7670008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slobodni teritorij Trsta |
E173723
|
entity |
| Predicate | hasSerboCroatianName |
P29131
|
FINISHED |
| Object | Slobodni teritorij Trsta |
—
|
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: Slobodni teritorij Trsta | Statement: [Slobodni teritorij Trsta, hasSerboCroatianName, Slobodni teritorij Trsta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSerboCroatianName Context triple: [Slobodni teritorij Trsta, hasSerboCroatianName, Slobodni teritorij Trsta]
-
A.
nameInSerbianCyrillic
Indicates that an entity’s name is written in the Serbian Cyrillic script.
-
B.
SerbianName
Indicates that an entity has a name that is of Serbian origin or used in the Serbian language.
-
C.
languageNameSerbianLatin
Indicates that the specified language name is written in Serbian using the Latin script.
-
D.
hasNameInSlavonic
Indicates that an entity has a specific name or designation expressed in a Slavonic language.
-
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_69c699562484819086752091e3164a27 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7063dab1881909598b04999b8b690 |
completed | March 27, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69c7015f7430819099d3ea2781b7cee2 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4 p.m.