Triple
T18157034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monaco Heliport |
E434657
|
entity |
| Predicate | hasTaxiConnections |
P24209
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Monaco Heliport, hasTaxiConnections, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTaxiConnections Context triple: [Monaco Heliport, hasTaxiConnections, yes]
-
A.
hasTaxiStand
chosen
Indicates that a location or facility includes or is served by a designated taxi stand area where taxis can wait for passengers.
-
B.
hasTransitAccessTo
Indicates that one place or entity is reachable from another via public or shared transportation services.
-
C.
hasPublicTransportConnection
Indicates that there is an available public transportation link or service connecting the related entities.
-
D.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
E.
hasHelicopterTransferConnection
Indicates that there is a transfer connection between two locations or services that is specifically made by helicopter.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4debf43348190a22f23a4bbfab433 |
completed | April 19, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.