Triple
T37278916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French naval base network |
E925323
|
entity |
| Predicate | mainAtlanticBase |
P2909
|
FINISHED |
| Object | Brest 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: Brest naval base | Statement: [French naval base network, mainAtlanticBase, Brest naval base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainAtlanticBase Context triple: [French naval base network, mainAtlanticBase, Brest naval base]
-
A.
mainBase
chosen
Indicates that one entity serves as the primary or central base or headquarters for another entity.
-
B.
easternBaseOf
Indicates that one entity is located at or forms the eastern base or foot of another entity.
-
C.
terminusCityOnAtlantic
Indicates that the city serves as a terminus (end point) of a route or line and is located on the Atlantic coast.
-
D.
mainIslandNetwork
Indicates that an entity belongs to or is part of the primary or central island network within a larger geographic or infrastructural system.
-
E.
mainPortInAmericas
Indicates that the entity serves as the primary or most significant port located within the Americas for another entity or operation.
- 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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.