Triple
T32073458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Force de frappe |
E819077
|
entity |
| Predicate | seaBasedComponent |
P41563
|
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: [Force de frappe, seaBasedComponent, Force océanique stratégique]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seaBasedComponent Context triple: [Force de frappe, seaBasedComponent, Force océanique stratégique]
-
A.
marineComponent
Indicates a relationship where something is a part, subsystem, or element of a marine or sea-related system, structure, or environment.
-
B.
locatedAtSea
Indicates that something exists or is situated in or on the sea.
-
C.
seaRepresents
Indicates that one entity serves as a symbolic, visual, or conceptual representation of another within a maritime or sea-related context.
-
D.
seaLegSystem
Indicates a system or mechanism that enables stable movement or support in a marine or sea-based environment.
-
E.
hasNavalComponent
chosen
Indicates that something includes, involves, or is associated with a naval or maritime element as part of its composition or structure.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b52a053c8190ae0898cb78b76688 |
completed | May 3, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:23 a.m.