Triple
T1363715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secret City |
E29154
|
entity |
| Predicate | startUseAsCodename |
P13305
|
FINISHED |
| Object | 1942 |
—
|
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: 1942 | Statement: [Secret City, startUseAsCodename, 1942]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startUseAsCodename Context triple: [Secret City, startUseAsCodename, 1942]
-
A.
codenameUser
Indicates that a user is assigned or associated with a particular codename.
-
B.
translationOfCodename
Indicates that one codename is a translated version of another codename, preserving its intended meaning across languages.
-
C.
hasCodenameLanguage
Indicates that a codename is expressed or defined in a particular language.
-
D.
nameUsedIn
chosen
Indicates that a particular name is employed or referenced within a specified context, work, or usage setting.
-
E.
hasCodeName
Indicates that an entity is known or referred to by a particular alternative name or alias, often used for secrecy or distinction.
- 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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c2b5d05c81908b49e282648e073a |
completed | March 1, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69a4bef945c08190a027472fdd695ea5 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:57 p.m.