Triple

T34147372
Position Surface form Disambiguated ID Type / Status
Subject USS America (CV-66) E875897 entity
Predicate airWing P30735 FINISHED
Object Carrier Air Wing 6
Carrier Air Wing 6 was a U.S. Navy aviation unit composed of multiple squadrons of carrier-based aircraft that conducted air operations from aircraft carriers during its service.
E2086308 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: Carrier Air Wing 6 | Statement: [USS America (CV-66), airWing, Carrier Air Wing 6]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Carrier Air Wing 6
Triple: [USS America (CV-66), airWing, Carrier Air Wing 6]
Generated description
Carrier Air Wing 6 was a U.S. Navy aviation unit composed of multiple squadrons of carrier-based aircraft that conducted air operations from aircraft carriers during its service.

Provenance (5 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_69f349abaa508190a820f206620efddc completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f70f91c2ec8190a7ff6051f89b5d31 completed May 3, 2026, 9:04 a.m.
NED1 Entity disambiguation (via context triple) batch_6a36cc74624c8190a4e037084467f9e3 completed June 20, 2026, 5:23 p.m.
NEDg Description generation batch_6a36cdae40b88190885e36cb022ca093 completed June 20, 2026, 5:28 p.m.
NED2 Entity disambiguation (via description) batch_6a36cef73ae4819087a176198cd876b0 completed June 20, 2026, 5:33 p.m.
Created at: May 1, 2026, 1:54 a.m.