Triple
T36261640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOLOMON |
E892102
|
entity |
| Predicate | associatedWithHubAirport |
P134018
|
FINISHED |
| Object | Honiara International Airport |
E48257
|
NE 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: Honiara International Airport | Statement: [SOLOMON, associatedWithHubAirport, Honiara International Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithHubAirport Context triple: [SOLOMON, associatedWithHubAirport, Honiara International Airport]
-
A.
associatedHubAirport
chosen
Indicates that one entity serves as a primary or hub airport functionally linked to the other entity.
-
B.
associatedWithAirportName
Indicates a relationship where an entity is linked or connected to a specific airport by its name.
-
C.
associatedWithAirportCode
Indicates that one entity has a relationship or connection to an airport identified by a specific airport code.
-
D.
associatedAirportPrimaryHubFor
Indicates that an airport serves as the primary hub for a particular airline or transportation operator.
-
E.
associatedAirport
Indicates a relationship where an entity is linked or connected to a specific airport, typically as its relevant or corresponding airport.
- F. None of above.
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_69f76e4699188190af045b11a840ce31 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39a30fd408819089ac87de6d3e812d |
completed | June 22, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.