Triple
T25786073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Virginia (SSN-774) |
E649419
|
entity |
| Predicate | succeededByVariant |
P157819
|
FINISHED |
| Object | Virginia Block II |
—
|
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 Block II | Statement: [USS Virginia (SSN-774), succeededByVariant, Virginia Block II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededByVariant Context triple: [USS Virginia (SSN-774), succeededByVariant, Virginia Block II]
-
A.
followOnVariant
chosen
Indicates that one entity is a subsequent or derived variant that follows from another entity in a sequence or evolution.
-
B.
exportVariantOf
Indicates that one entity is an exported version or externally released form derived from another, original entity.
-
C.
succeededByEvent
Indicates that one event directly follows and replaces another in a temporal or sequential order.
-
D.
introducedAsSuccessorOf
Indicates that one entity was formally presented or designated to take over the role, position, or function previously held by another entity.
-
E.
succeededByContext
Indicates that one context or situation directly follows and replaces another in a sequence or progression.
- 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_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 22, 2026, 5:55 a.m.