Triple
T2417893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French Submarine Forces |
E52348
|
entity |
| Predicate | introducedNuclearSubmarines |
P38422
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [French Submarine Forces, introducedNuclearSubmarines, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedNuclearSubmarines Context triple: [French Submarine Forces, introducedNuclearSubmarines, 1960s]
-
A.
nuclearPowered
Indicates that something operates using nuclear energy as its primary power source.
-
B.
engagedSubmarines
Indicates that one entity took hostile or combat action against submarines belonging to another entity.
-
C.
antiSubmarineArmament
Indicates the type or presence of weapons or equipment specifically designed for anti-submarine warfare associated with an entity.
-
D.
hasFirstConfirmedSubmarineArrivalVessel
Indicates that a vessel is the first one confirmed to have arrived at a location by submarine.
-
E.
nuclearWeaponsProgram
Indicates the existence, development, or pursuit of a program related to the research, production, or maintenance of nuclear weapons.
- 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_69ab495622948190bc6bc6e4cddaf645 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc9f342e88190a430b02842ded418 |
completed | March 7, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69abc5a889948190b77de4ef6ac815a8 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc9f1ba608190b488874bed3533dd |
completed | March 7, 2026, 6:47 a.m. |
Created at: March 6, 2026, 9:42 p.m.