Triple
T17314500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PAFA |
E420384
|
entity |
| Predicate | supportsFloatplaneOperations |
P37751
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [PAFA, supportsFloatplaneOperations, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsFloatplaneOperations Context triple: [PAFA, supportsFloatplaneOperations, true]
-
A.
hasSeaplaneFacilities
chosen
Indicates that a location or facility provides infrastructure and services specifically for the operation, docking, or handling of seaplanes.
-
B.
operatesFlightsTo
Indicates that one entity (typically an airline) runs or provides flight services to the location represented by the other entity.
-
C.
hasSeaplaneFacilitiesNearby
Indicates that the subject has seaplane facilities located in its nearby vicinity.
-
D.
servesFlightsTo
Indicates that one transportation provider regularly operates flights to a specified destination location.
-
E.
isAviationElementOf
Indicates that something functions as a component or constituent part within a broader aviation-related system, structure, or context.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4399b4dcc8190996d79d04ba88795 |
completed | April 19, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:43 a.m.