Triple
T29533798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZNA |
E749278
|
entity |
| Predicate | waterAirport |
P182240
|
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: [ZNA, waterAirport, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterAirport Context triple: [ZNA, waterAirport, true]
-
A.
airportUse
Indicates that an airport is used or utilized by a particular entity, such as an airline, organization, or service.
-
B.
airportIsland
Indicates that an airport is located on, or associated with, an island.
-
C.
usesAirportCode
Indicates that one entity employs or identifies an airport by a specific standardized airport code.
-
D.
airportServesAs
Indicates that an airport functions in a particular role or capacity (such as primary, secondary, or hub) for a specified area, organization, or service.
-
E.
airportLocatedWithin
Indicates that an airport is geographically situated inside the boundaries of a specified area or region.
- 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_69f0bd47abb081909bd6e6a33d770fd8 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7886b27f08190ab4580f949222c93 |
completed | May 3, 2026, 5:39 p.m. |
Created at: April 28, 2026, 4:56 p.m.