Triple
T35790654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Nimitz Carrier Strike Group |
E1034682
|
entity |
| Predicate | typicalEmbarkedAirWing |
P32852
|
FINISHED |
| Object | Carrier Air Wing |
—
|
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: Carrier Air Wing | Statement: [USS Nimitz Carrier Strike Group, typicalEmbarkedAirWing, Carrier Air Wing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEmbarkedAirWing Context triple: [USS Nimitz Carrier Strike Group, typicalEmbarkedAirWing, Carrier Air Wing]
-
A.
typicalEmbarkedForce
chosen
Indicates the usual or characteristic military force that is boarded onto a vehicle, vessel, or transport platform for an operation or mission.
-
B.
embarkedAircraft
Indicates that one entity boarded or got onto an aircraft as a passenger or occupant.
-
C.
designedToEmbark
Indicates that something is created or configured with the specific purpose of beginning or initiating a journey, process, or undertaking.
-
D.
shipSurvived
Indicates that a ship remained intact and continued to exist or operate after a potentially destructive event or period.
-
E.
shipBoardedFrom
Indicates that an entity boarded a ship originating from or at a specified location or source.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.