Triple
T32795818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Coral Sea (CV-43) |
E838759
|
entity |
| Predicate | airWingCarried |
P175126
|
FINISHED |
| Object | Carrier Air Wing 15 |
—
|
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: Carrier Air Wing 15 | Statement: [USS Coral Sea (CV-43), airWingCarried, Carrier Air Wing 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airWingCarried Context triple: [USS Coral Sea (CV-43), airWingCarried, Carrier Air Wing 15]
-
A.
airWingType
Indicates the classification or category of an air wing associated with an entity.
-
B.
airWingCapacity
Indicates the maximum number or volume of aircraft or air operations that an air wing can support or handle.
-
C.
aircraftTypesCarried
Indicates that one entity (typically a vessel, facility, or platform) carries or is capable of carrying specific types of aircraft as part of its operations or configuration.
-
D.
usesCarrierAircraft
Indicates that one entity employs or operates aircraft that are designed to be launched from and recovered by an aircraft carrier.
-
E.
carriedBy
Indicates that one entity is physically supported and transported by another entity.
- 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_69f3493c7f6881908edf2aa13631d1e0 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6ce6c76bc8190b865343d3f5810c9 |
completed | May 3, 2026, 4:26 a.m. |
Created at: May 1, 2026, 1:14 a.m.