Triple
T25273070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Wasp (CV-18) |
E633617
|
entity |
| Predicate | successorNameCarrier |
P33571
|
FINISHED |
| Object | USS Wasp (LHD-1) |
—
|
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 Wasp (LHD-1) | Statement: [USS Wasp (CV-18), successorNameCarrier, USS Wasp (LHD-1)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorNameCarrier Context triple: [USS Wasp (CV-18), successorNameCarrier, USS Wasp (LHD-1)]
-
A.
successorNamesake
chosen
Indicates that one entity is named after another entity that precedes it, typically as its successor or continuation in name.
-
B.
successorNameInService
Indicates that one entity is the name of the successor that takes over a role, position, or function within a particular service or service context.
-
C.
successorFullName
Indicates that one entity is the full name of the successor of another entity (e.g., the person or role that follows it).
-
D.
successorNameForm
Indicates that the object is the name or naming form used for the successor entity that follows the subject in a sequence or lineage.
-
E.
nicknameOfSuccessor
Indicates that one entity is a nickname or informal name used to refer to another entity that is its successor.
- 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 21, 2026, 1:17 p.m.