Triple
T25785953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSN(X)-class submarine |
E649417
|
entity |
| Predicate | plannedToSucceed |
P43223
|
FINISHED |
| Object | Virginia-class submarine |
—
|
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: Virginia-class submarine | Statement: [SSN(X)-class submarine, plannedToSucceed, Virginia-class submarine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedToSucceed Context triple: [SSN(X)-class submarine, plannedToSucceed, Virginia-class submarine]
-
A.
planned
Indicates that an entity has intentionally arranged or scheduled another entity or event to occur in the future.
-
B.
maySucceed
Indicates that one entity has the potential or possibility to follow or replace another in a role, position, or sequence.
-
C.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
-
D.
succeedsTo
chosen
Indicates that one entity takes over a role, position, or function previously held by another entity, following it in sequence or authority.
-
E.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 22, 2026, 5:54 a.m.