Triple
T11649839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Spring Tide |
E276872
|
entity |
| Predicate | hasCodenameFor |
P61115
|
FINISHED |
| Object | plans for accession of Charles III |
—
|
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: plans for accession of Charles III | Statement: [Operation Spring Tide, hasCodenameFor, plans for accession of Charles III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCodenameFor Context triple: [Operation Spring Tide, hasCodenameFor, plans for accession of Charles III]
-
A.
hasCodenameLanguage
Indicates that a codename is expressed or defined in a particular language.
-
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.
relatedCodename
Indicates that one entity has an associated or connected codename that is contextually related to it.
-
D.
usesCodeName
chosen
Indicates that one entity refers to another entity by a code name or alias instead of its real or full designation.
-
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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a2cea9308190a13f7dd995ea07a4 |
completed | April 10, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.