Triple
T35313468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ULTRA |
E1019840
|
entity |
| Predicate | hasCodenameType |
P2396
|
FINISHED |
| Object | wartime codename |
—
|
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: wartime codename | Statement: [ULTRA, hasCodenameType, wartime codename]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCodenameType Context triple: [ULTRA, hasCodenameType, wartime codename]
-
A.
hasCodeName
Indicates that an entity is known or referred to by a particular alternative name or alias, often used for secrecy or distinction.
-
B.
hasCodenameLanguage
Indicates that a codename is expressed or defined in a particular language.
-
C.
hasCodenameSeries
Indicates that an entity is associated with, or belongs to, a particular codename-based series.
-
D.
hasTypeName
chosen
Indicates that an entity is associated with a specific type name used to classify or identify its kind.
-
E.
takesCodenameFrom
Indicates that one entity adopts or derives its codename from another entity.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.