Triple
T26045685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Wilmington (CL-79) |
E647820
|
entity |
| Predicate | hasSuccessorShip |
P177287
|
FINISHED |
| Object | USS Cabot (CVL-28) |
—
|
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: USS Cabot (CVL-28) | Statement: [USS Wilmington (CL-79), hasSuccessorShip, USS Cabot (CVL-28)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuccessorShip Context triple: [USS Wilmington (CL-79), hasSuccessorShip, USS Cabot (CVL-28)]
-
A.
successorShipIdentity
Indicates that one entity is recognized as the direct successor or continuation of another, preserving its identity across the transition.
-
B.
hasFlagshipSuccessor
Indicates that one entity serves as the primary or leading successor to another, typically replacing it as the main or flagship version, product, or instance.
-
C.
hasCitySuccessor
Indicates that one city is the successor or replacement of another city, typically in terms of status, function, or administrative role.
-
D.
hasSuccessorUsers
Indicates that one user or set of users is followed or replaced by another user or set of users in a sequence or succession.
-
E.
hasSuccessorScheme
Indicates that one scheme is the direct successor or follow-up to another scheme in a sequence or versioning relationship.
- 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_69e77e8d419481908004e6318d28aaab |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6fb93224881908fc66fe76115fcdb |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fb17d5ec81909091e37e1ddbe577 |
completed | May 3, 2026, 7:36 a.m. |
Created at: April 22, 2026, 9:10 a.m.