Triple
T4393063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .si |
E99410
|
entity |
| Predicate | registrationEntities |
P22585
|
FINISHED |
| Object | accredited registrars |
—
|
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: accredited registrars | Statement: [.si, registrationEntities, accredited registrars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registrationEntities Context triple: [.si, registrationEntities, accredited registrars]
-
A.
registrationSystem
Indicates a system or process responsible for recording, managing, and maintaining registrations or enrollments for entities.
-
B.
relatedRegister
Indicates a relationship where one entity is associated with, linked to, or corresponds to a particular register or record in a system.
-
C.
registrationContext
Indicates the situational or environmental context under which a registration event occurs, such as conditions, purpose, or setting.
-
D.
registrationCategory
Indicates the classification or type under which an entity is formally registered within a system or registry.
-
E.
memberEntities
chosen
Indicates that certain entities belong to, or are included as members within, a larger group or collection.
- 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.