Triple
T2023347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trident nuclear missile system |
E44152
|
entity |
| Predicate | basingMode |
P34589
|
FINISHED |
| Object | sea-based |
—
|
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: sea-based | Statement: [Trident nuclear missile system, basingMode, sea-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basingMode Context triple: [Trident nuclear missile system, basingMode, sea-based]
-
A.
baselineType
Indicates the type or category of a baseline used as a reference point for comparison or evaluation.
-
B.
potentialBasing
Indicates a relationship where one entity could serve as the base, foundation, or supporting location for another, but this basing has not yet been realized or confirmed.
-
C.
areBasedOn
Indicates that one entity is founded, derived, or developed from the principles, content, or structure of another entity.
-
D.
isBasedOn
Indicates that one entity is derived from, inspired by, or developed using the content, structure, or principles of another entity.
-
E.
baseType
Indicates that one entity serves as the underlying or parent type from which another entity is derived or specialized.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8f1728481909ae36e821b9edef2 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a389408190a84a54856352f15b |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb83e7888819096dc40275c77daff |
completed | March 7, 2026, 5:31 a.m. |
Created at: March 4, 2026, 7:38 p.m.