Triple
T38217622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Venom |
E1010726
|
entity |
| Predicate | firstFlightTest |
P2088
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Sea Venom, firstFlightTest, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstFlightTest Context triple: [Sea Venom, firstFlightTest, 2017]
-
A.
firstIntegratedFlightTest
Indicates that the event is the initial combined test flight of multiple integrated components or systems.
-
B.
firstFlight
chosen
Indicates that the associated event or record corresponds to the earliest or initial flight taken or performed by the referenced entity.
-
C.
firstFreeFlightTest
Indicates that the event is the initial instance in which an aircraft, spacecraft, or similar vehicle is flown freely without external constraints or tethering.
-
D.
firstPoweredFlightDate
Indicates the calendar date on which an entity (typically an aircraft or spacecraft) achieved its first powered flight.
-
E.
firstUncrewedTestFlight
Indicates the event of conducting the initial test flight of a vehicle or system without any crew onboard.
- 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.