Triple
T27207658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sverdlovsk-44 |
E683908
|
entity |
| Predicate | hasAccessStatus |
P32027
|
FINISHED |
| Object | restricted |
—
|
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: restricted | Statement: [Sverdlovsk-44, hasAccessStatus, restricted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessStatus Context triple: [Sverdlovsk-44, hasAccessStatus, restricted]
-
A.
hasRightsStatus
Indicates that an entity is associated with a particular legal or usage rights condition or status.
-
B.
hasHumanAccess
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
-
C.
accessStatus
chosen
Indicates the current level or state of permission or availability for accessing a resource or entity.
-
D.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
E.
hasAuthorityStatus
Indicates that one entity holds a particular level or type of official power, control, or decision-making authority over another entity or within a defined context.
- 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 9:38 a.m.