Triple
T37278917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French naval base network |
E925323
|
entity |
| Predicate | mainChannelBase |
P194787
|
FINISHED |
| Object | Cherbourg naval base |
—
|
NE NERFINISHED |
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: Cherbourg naval base | Statement: [French naval base network, mainChannelBase, Cherbourg naval base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainChannelBase Context triple: [French naval base network, mainChannelBase, Cherbourg naval base]
-
A.
coreChannel
Indicates a primary or central communication channel through which key information, signals, or interactions are transmitted.
-
B.
ownedChannel
Indicates that one entity possesses ownership or control over a particular channel.
-
C.
primaryChannel
Indicates that one channel is designated as the main or most important channel among a set of available channels.
-
D.
originalChannel
Indicates the communication channel or medium through which something was first created, sent, or published.
-
E.
targetChannel
Indicates the specific channel or medium through which an action, message, or effect is directed toward its intended recipient.
- F. None of above. chosen
Provenance (4 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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
| PDg | Predicate description generation | batch_69fd8640e1d4819081c98f15eeb221ab |
completed | May 8, 2026, 6:44 a.m. |
Created at: May 3, 2026, 4:16 p.m.