Triple
T37028357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DCN Cherbourg |
E916417
|
entity |
| Predicate | hasBuiltFor |
P8196
|
FINISHED |
| Object | Force océanique stratégique |
—
|
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: Force océanique stratégique | Statement: [DCN Cherbourg, hasBuiltFor, Force océanique stratégique]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuiltFor Context triple: [DCN Cherbourg, hasBuiltFor, Force océanique stratégique]
-
A.
hasBuilt
Indicates that one entity is the creator or constructor of another entity.
-
B.
hasBuild
Indicates that one entity has constructed, created, or assembled another entity.
-
C.
wasBuilt
Indicates that one entity constructed, created, or assembled another entity, typically at a specific time or over a period.
-
D.
hasBuiltEnvironment
Indicates that an entity possesses, contains, or is associated with human-made physical structures or infrastructure in its environment.
-
E.
isBuiltFor
chosen
Indicates that one entity is specifically designed, intended, or optimized to serve, support, or accommodate another entity or purpose.
- 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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: May 3, 2026, 4:14 p.m.