Triple
T27178439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sverdlovsk-45 |
E683118
|
entity |
| Predicate | hadCodeName |
P6015
|
FINISHED |
| Object | Sverdlovsk-45 |
—
|
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: Sverdlovsk-45 | Statement: [Sverdlovsk-45, hadCodeName, Sverdlovsk-45]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadCodeName Context triple: [Sverdlovsk-45, hadCodeName, Sverdlovsk-45]
-
A.
hasCodeName
chosen
Indicates that an entity is known or referred to by a particular alternative name or alias, often used for secrecy or distinction.
-
B.
usesCodeName
Indicates that one entity refers to another entity by a code name or alias instead of its real or full designation.
-
C.
codenameOwner
Indicates that one entity is the designated owner or holder of the specified codename associated with another entity.
-
D.
testCodeName
Indicates that an entity is identified or referred to by a specific test code name.
-
E.
codenameUser
Indicates that a user is assigned or associated with a particular codename.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 9:27 a.m.