Triple
T5257641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Air Force Thunderbirds |
E118739
|
entity |
| Predicate | signatureManeuver |
P62555
|
FINISHED |
| Object | diamond formation |
—
|
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: diamond formation | Statement: [United States Air Force Thunderbirds, signatureManeuver, diamond formation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureManeuver Context triple: [United States Air Force Thunderbirds, signatureManeuver, diamond formation]
-
A.
signatureEvent
Indicates an event in which an entity formally signs or authorizes something, such as a document, agreement, or record.
-
B.
signatureImage
Indicates that an entity has an associated image that visually represents its signature.
-
C.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
D.
signatureFeature
Indicates that one entity is a defining or characteristic feature that distinctly identifies or typifies another entity.
-
E.
signatureWork
Indicates that the work is a defining or most representative creation associated with an entity (such as a person, group, or organization).
- 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_69bd446978108190bb5f9c5c23d93f88 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bcced6881909bdb7ac5471a37fe |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd7bcabe58819096255672664513b1 |
completed | March 20, 2026, 4:54 p.m. |
Created at: March 20, 2026, 1:50 p.m.