Triple
T18019825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pointe-à-Pitre International Airport |
E431087
|
entity |
| Predicate | IATA code |
P2569
|
FINISHED |
| Object | PTP |
—
|
NE NERFINISHED |
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: PTP | Statement: [Pointe-à-Pitre International Airport, IATA code, PTP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PTP Context triple: [Pointe-à-Pitre International Airport, IATA code, PTP]
-
A.
PTP
PTP is a network-based time synchronization protocol defined by the IEEE 1588 standard that enables highly precise clock alignment across distributed systems.
-
B.
PTP
PTP is a standardized protocol used to transfer digital images from cameras and other imaging devices to computers and other hosts.
-
C.
PTP
chosen
PTP is the IATA airport code for Pointe-à-Pitre International Airport, the main air gateway to Guadeloupe in the Caribbean.
-
D.
PTP/IP
PTP/IP is a network-based extension of the Picture Transfer Protocol that enables transferring images and related data over IP networks such as Wi‑Fi or Ethernet.
-
E.
PT
PT is the time standard used along the west coast of North America, including cities like Los Angeles, San Francisco, and Vancouver.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b9c09fdc819097a7fa07d44b0505 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 10:24 a.m.