Triple
T30989029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Akron (ZRS-4) |
E789615
|
entity |
| Predicate | aircraftHandlingSystem |
P175281
|
FINISHED |
| Object | trapeze system |
—
|
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: trapeze system | Statement: [USS Akron (ZRS-4), aircraftHandlingSystem, trapeze system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftHandlingSystem Context triple: [USS Akron (ZRS-4), aircraftHandlingSystem, trapeze system]
-
A.
aircraftControlType
Indicates the type or method of control used to operate or direct an aircraft.
-
B.
flyByWire
Indicates a control relationship where an aircraft’s control surfaces are operated by electronic signals rather than direct mechanical linkage from the pilot.
-
C.
controlsPhaseOfFlight
Indicates that one entity has authority over or manages a specific phase of another entity’s flight operation.
-
D.
aircraftCommanded
Indicates that one entity serves as the commanding officer or leader in charge of operating, directing, or overseeing the other entity, which is an aircraft.
-
E.
flightMechanic
Indicates that one entity serves as a mechanic responsible for maintaining or repairing the aircraft associated with 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_69f224c550b081909ddfceb0c3d03bdd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cee3604c81908a07eade2f39064e |
completed | May 3, 2026, 4:28 a.m. |
Created at: April 29, 2026, 8:56 p.m.