Triple
T10891948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latham’s snipe |
E257197
|
entity |
| Predicate | flightDisplay |
P96260
|
FINISHED |
| Object | aerial display with zig-zag flight |
—
|
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: aerial display with zig-zag flight | Statement: [Latham’s snipe, flightDisplay, aerial display with zig-zag flight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flightDisplay Context triple: [Latham’s snipe, flightDisplay, aerial display with zig-zag flight]
-
A.
flightRecord
Indicates a record of a specific flight event or journey, capturing details about its occurrence and characteristics.
-
B.
flightOver
Indicates that one entity moves through the air above or across another entity or area.
-
C.
flightPhase
Indicates the specific stage or phase of an aircraft’s operation within a flight (e.g., taxi, takeoff, climb, cruise, descent, landing).
-
D.
airTraffic
Indicates the movement and flow of aircraft through airspace, including their routes, density, and interactions while in flight.
-
E.
aircraftStatus
Indicates the current operational condition or state of an aircraft (e.g., active, grounded, in maintenance, or decommissioned).
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75206354881908b148f2df3938513 |
completed | April 9, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101de31c819090707635f6790559 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:21 p.m.