Triple
T20278285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Lucia railway station area |
E503070
|
entity |
| Predicate | typicalArrivalPointFor |
P131665
|
FINISHED |
| Object | tourists visiting Venice |
—
|
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: tourists visiting Venice | Statement: [Santa Lucia railway station area, typicalArrivalPointFor, tourists visiting Venice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalArrivalPointFor Context triple: [Santa Lucia railway station area, typicalArrivalPointFor, tourists visiting Venice]
-
A.
isMainArrivalPointFor
chosen
Indicates that a location serves as the primary arrival point for a given entity or flow of entities.
-
B.
transportTerminusFor
Indicates that a location serves as the endpoint or final stop for a particular transport route or service.
-
C.
typicalDestinationAirportIATA
Indicates the IATA airport code that is typically the destination in this kind of trip or route.
-
D.
arrivalLocationType
Indicates the type or category of place where an arrival occurs in the described relationship or event.
-
E.
arrivalAt
Indicates the event or state of an entity reaching and being present at a specific destination or location.
- 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_69e0b4b0e79c8190bd61f22ef1329fa8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e675e59f7c819086638b871ecbbd40 |
completed | April 20, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 10:35 a.m.