Triple
T35790634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Nimitz Carrier Strike Group |
E1034682
|
entity |
| Predicate | typicalCruiserType |
P109622
|
FINISHED |
| Object | Ticonderoga-class guided-missile cruiser |
E1001819
|
NE 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: Ticonderoga-class guided-missile cruiser | Statement: [USS Nimitz Carrier Strike Group, typicalCruiserType, Ticonderoga-class guided-missile cruiser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCruiserType Context triple: [USS Nimitz Carrier Strike Group, typicalCruiserType, Ticonderoga-class guided-missile cruiser]
-
A.
typicalShipTypes
chosen
Indicates that the subject is commonly or characteristically associated with the specified types or categories of ships.
-
B.
craftType
Indicates the specific kind or category of craft or vessel associated with an entity.
-
C.
navalStandardType
Indicates the specific naval standard or classification system under which an entity (such as a vessel, equipment, or procedure) is defined or regulated.
-
D.
typicalShipStrength
Indicates the usual or characteristic level of strength or power associated with a given ship.
-
E.
shipClass
Indicates the classification or type category to which a particular ship belongs.
- F. None of above.
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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a389162047881908710fcaf86a56a19 |
completed | June 22, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.