Triple
T30277521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sakhalin Regional Drama Theater |
E769991
|
entity |
| Predicate | isRegionalInstitution |
P136946
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sakhalin Regional Drama Theater, isRegionalInstitution, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRegionalInstitution Context triple: [Sakhalin Regional Drama Theater, isRegionalInstitution, true]
-
A.
regionOfInstitution
Indicates that a specified region is the geographic area in which an institution is located or operates.
-
B.
isPublicInstitution
Indicates that an entity operates as a publicly governed or state-funded institution, typically serving the general public under public law or oversight.
-
C.
hasLocalInstitution
Indicates that a given place or region possesses or hosts an institution that operates locally within its boundaries.
-
D.
isInstitutional
chosen
Indicates that an entity functions as or is classified as an institution within the given context.
-
E.
inInstitution
Indicates that an entity is located within, belongs to, or is formally associated with a particular institution.
- 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_69f224868fa8819099127eaf8855a28f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f680d983608190a05ee341096d3c6c |
completed | May 2, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:44 p.m.