Triple
T9388435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark 8 torpedo |
E225960
|
entity |
| Predicate | continuedService |
P69802
|
FINISHED |
| Object | post–World War II |
—
|
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: post–World War II | Statement: [Mark 8 torpedo, continuedService, post–World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuedService Context triple: [Mark 8 torpedo, continuedService, post–World War II]
-
A.
continuedInServiceOn
chosen
Indicates that an entity remained active, operational, or in use beyond a specified point in time or event.
-
B.
continuedBy
Indicates that one entity carries on, extends, or resumes the activity, process, or sequence initiated by another entity.
-
C.
mainUseContinued
Indicates that the primary use or function of something persists or remains in effect over a subsequent period.
-
D.
primaryContinuityOf
Indicates that one entity serves as the main or principal continuation or extension of another entity in a sequence or process.
-
E.
continuedOnNetwork
Indicates that an entity (such as a show, series, or program) remained in production or broadcast on the same network beyond a given point in time.
- 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_69ca842e9dcc8190a264119e683cfe04 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50d6e5f081908102909cb4cbb649 |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:45 p.m.