Triple
T24140453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiat AS.5 |
E598214
|
entity |
| Predicate | designedForAircraftType |
P30181
|
FINISHED |
| Object | seaplanes |
—
|
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: seaplanes | Statement: [Fiat AS.5, designedForAircraftType, seaplanes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForAircraftType Context triple: [Fiat AS.5, designedForAircraftType, seaplanes]
-
A.
usedByAircraftType
chosen
Indicates that something (such as equipment, infrastructure, or a procedure) is employed or operated by a specific type or category of aircraft.
-
B.
intendedAircraft
Indicates that an aircraft is the one planned or designated to be used for a particular flight, mission, or operation.
-
C.
appliedToAircraftDesignedBy
Indicates that something (such as a component, system, or regulation) is applied to an aircraft that was designed by a specified designer or organization.
-
D.
usedOnAircraftName
Indicates that something is employed or applied on an aircraft identified by a specific name.
-
E.
supportsAircraft
Indicates that one entity is capable of accommodating, carrying, or enabling the operation of an aircraft.
- 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e005f7f48190b2c538bfc79a83b2 |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:28 p.m.