Triple
T351945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Sea Lion |
E7461
|
entity |
| Predicate | languageOfCodename |
P15
|
FINISHED |
| Object | German |
—
|
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: German | Statement: [Operation Sea Lion, languageOfCodename, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfCodename Context triple: [Operation Sea Lion, languageOfCodename, German]
-
A.
languageOfWorkOrName
chosen
Indicates the language in which a work is created or a name is expressed.
-
B.
languageCodeISO639-2
Indicates that an entity is associated with a language identified by its ISO 639-2 three-letter code.
-
C.
languageCodeISO639-1
Indicates that the subject entity is associated with the specified two-letter ISO 639-1 language code.
-
D.
languageOfOperation
Indicates the language in which an entity (such as a system, service, or process) primarily operates or functions.
-
E.
languageBranch
Indicates that one language belongs to, or is classified under, a broader linguistic branch or subgroup.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb7f1be88190964ddcbb6a05f021 |
completed | Feb. 28, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69a2e9571bd88190b6fcb16f21604720 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.