Triple
T31251999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brace Up! |
E796848
|
entity |
| Predicate | hasSettingInOriginalWork |
P146130
|
FINISHED |
| Object | Russia |
—
|
NE NERFINISHED |
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: Russia | Statement: [Brace Up!, hasSettingInOriginalWork, Russia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSettingInOriginalWork Context triple: [Brace Up!, hasSettingInOriginalWork, Russia]
-
A.
hasOriginalWorkSetting
chosen
Indicates that an entity is associated with the setting or context in which the original work or source material takes place.
-
B.
usesOriginalWorkKey
Indicates that an entity makes use of, references, or is derived from another entity identified as the original work by a specific key.
-
C.
hasSettingOfOrigin
Indicates that something originates from, or was initially set in, a particular setting or environment.
-
D.
hasTitleInOriginalWork
Indicates that an entity holds a specific title or designation within its original work or source context.
-
E.
hasOriginalWorkMedium
Indicates that an original creative work is associated with a specific medium or material in which it was first produced.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
Created at: April 29, 2026, 9:11 p.m.