Triple
T15540089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HSTR |
E370451
|
entity |
| Predicate | aircraftPrimaryUse |
P2860
|
FINISHED |
| Object | passenger transport |
—
|
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: passenger transport | Statement: [HSTR, aircraftPrimaryUse, passenger transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftPrimaryUse Context triple: [HSTR, aircraftPrimaryUse, passenger transport]
-
A.
primaryAircraftRole
chosen
Indicates the main operational function or mission type an aircraft is primarily designed or used to perform.
-
B.
notableAircraftRole
Indicates that an aircraft is notably associated with performing a particular role or function.
-
C.
aviationUsage
Indicates that something is used for, involved in, or associated with aviation-related activities or purposes.
-
D.
poweredAircraftRole
Indicates the functional role or purpose assigned to a powered (engine-driven) aircraft within an operation or context.
-
E.
aircraftRoleSpecialization
Indicates that one aircraft role is a more specific, specialized form of another, more general aircraft role.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04430b5188190a555a3cd4fb0c61c |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:07 a.m.