Triple
T4393068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .si |
E99410
|
entity |
| Predicate | languageOfRegistryWebsite |
P16555
|
FINISHED |
| Object | Slovene |
—
|
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: Slovene | Statement: [.si, languageOfRegistryWebsite, Slovene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfRegistryWebsite Context triple: [.si, languageOfRegistryWebsite, Slovene]
-
A.
languageOfOfficialWebsite
chosen
Indicates the language in which an entity’s official website is primarily written or presented.
-
B.
languageOfLocalOrganization
Indicates the language used or officially adopted by a local organization in its operations or communications.
-
C.
languageOfJurisdiction
Indicates the language officially used for legal and administrative purposes within a given jurisdiction.
-
D.
governingLanguage
Indicates the language that holds official or authoritative status over a given entity, such as a region, organization, or document.
-
E.
languageOfDocumentation
Indicates the language in which the documentation for an entity is written or provided.
- 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_69b345506b408190b0e3dee616738a7d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352a8862481909dc67abf42be6928 |
completed | March 12, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:19 p.m.