Triple
T26837676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ROC |
E675681
|
entity |
| Predicate | prohibitedFromUsing |
P38719
|
FINISHED |
| Object | Russian national anthem |
—
|
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: Russian national anthem | Statement: [ROC, prohibitedFromUsing, Russian national anthem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prohibitedFromUsing Context triple: [ROC, prohibitedFromUsing, Russian national anthem]
-
A.
isProhibitedFor
chosen
Indicates that a certain action, object, or condition is not allowed or is forbidden for a specified entity or group.
-
B.
restrictedFromUseFor
Indicates that something is prohibited or limited from being used for a specified purpose, context, or application.
-
C.
prohibits
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
-
D.
workProhibited
Indicates that an entity is not allowed or is forbidden to perform a particular work or job activity.
-
E.
cannotBeUsedWithout
Indicates that one entity is dependent on another such that it cannot function, operate, or be utilized unless the other entity is also present or in use.
- 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 5:05 a.m.