Triple
T15851643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Short Empire flying boat |
E384353
|
entity |
| Predicate | airlineClass |
P120765
|
FINISHED |
| Object | luxury flying boat airliner |
—
|
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: luxury flying boat airliner | Statement: [Short Empire flying boat, airlineClass, luxury flying boat airliner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airlineClass Context triple: [Short Empire flying boat, airlineClass, luxury flying boat airliner]
-
A.
airlineCategory
Indicates the classification or type of an airline within a defined categorization system (e.g., full-service, low-cost, regional).
-
B.
seatClass
Indicates the travel or seating category assigned to a passenger or seat (e.g., economy, business, first class).
-
C.
airlineType
Indicates the classification or category of an airline based on its operational or service characteristics.
-
D.
aircraftSeatingCategory
Indicates the classification of an aircraft’s seating arrangement or capacity type associated with an entity.
-
E.
designatedAirlineType
Indicates that an airline has been assigned a specific operational or classification type for a given context or service.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142b976c081908d3ba3e705419f3a |
completed | April 16, 2026, 8:12 p.m. |
| PDg | Predicate description generation | batch_69e174da2c2c819099ec46616798245a |
completed | April 16, 2026, 11:46 p.m. |
Created at: April 10, 2026, 4:50 a.m.