Triple
T34752483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ticonderoga-class cruiser |
E1001819
|
entity |
| Predicate | leadShipLaunched |
P34263
|
FINISHED |
| Object | April 25, 1981 |
—
|
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: April 25, 1981 | Statement: [Ticonderoga-class cruiser, leadShipLaunched, April 25, 1981]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadShipLaunched Context triple: [Ticonderoga-class cruiser, leadShipLaunched, April 25, 1981]
-
A.
thirdShipLaunched
Indicates that an entity is the third ship to be launched in a particular sequence or context.
-
B.
originalShipLaunchedIn
Indicates that an original ship was first launched in a specified year, place, or context.
-
C.
vesselLaunched
Indicates that a vessel has been formally set afloat or put into operation at a specific time or place.
-
D.
commissionedShip
Indicates that a ship has been formally placed into active service, typically following its construction or acquisition.
-
E.
firstShip
chosen
Indicates that the subject is the earliest or initial ship associated with, created by, or used in relation to the object.
- 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_69f76db0fb30819096709d43f9a1f45f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.