Triple
T3911377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagasaki Airport |
E87327
|
entity |
| Predicate | alsoHandles |
P31626
|
FINISHED |
| Object | international flights |
—
|
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: international flights | Statement: [Nagasaki Airport, alsoHandles, international flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoHandles Context triple: [Nagasaki Airport, alsoHandles, international flights]
-
A.
canHandle
chosen
Indicates that an entity has the ability or capacity to manage, process, or deal with another entity or situation.
-
B.
alsoHolds
Indicates that a condition, property, or relation that applies in one context or case simultaneously applies in another context or case.
-
C.
alsoServedBy
Indicates that the same service, function, or role is additionally provided or fulfilled by another entity alongside the primary one.
-
D.
alsoRuns
Indicates that the subject, in addition to its primary or previously mentioned activity or role, performs or operates another activity, process, or entity.
-
E.
canAlsoBe
Indicates that something has an additional possible state, role, or classification beyond its primary one.
- 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_69aed9424514819086e9c58adde6652d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75cff148190b6d5979d17fae085 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.