Triple
T5306497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gothic Serpent |
E120114
|
entity |
| Predicate | codeNameType |
P1081
|
FINISHED |
| Object | U.S. military operation 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: U.S. military operation codename | Statement: [Gothic Serpent, codeNameType, U.S. military operation codename]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeNameType Context triple: [Gothic Serpent, codeNameType, U.S. military operation codename]
-
A.
usesCodeName
Indicates that one entity refers to another entity by a code name or alias instead of its real or full designation.
-
B.
hasCodeName
Indicates that an entity is known or referred to by a particular alternative name or alias, often used for secrecy or distinction.
-
C.
codenameUser
Indicates that a user is assigned or associated with a particular codename.
-
D.
nameType
chosen
Indicates the specific category or type of a name associated with an entity (e.g., legal name, nickname, alias, or preferred name).
-
E.
endUseAsCodename
Indicates that an entity stops being used as a codename for another entity or concept.
- 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_69bd44704be88190acdb2ac481b0ff55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd86f20f008190be7b5848af05f2b8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd84534f9c8190bc19d4812060768d |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:53 p.m.