Triple
T18467231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porta Praetoria |
E451195
|
entity |
| Predicate | touristInformationAvailable |
P54718
|
FINISHED |
| Object | on-site panels |
—
|
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: on-site panels | Statement: [Porta Praetoria, touristInformationAvailable, on-site panels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touristInformationAvailable Context triple: [Porta Praetoria, touristInformationAvailable, on-site panels]
-
A.
hasTouristSignage
Indicates that there is official signage present to guide or inform tourists about a place, route, or attraction.
-
B.
tourInformation
Indicates that an entity provides details or data about a tour, such as schedule, itinerary, or features.
-
C.
touristAccess
Indicates that a place or resource is available for use or visitation by tourists.
-
D.
visitorInformation
chosen
Indicates that information or details are provided for or about visitors in relation to a particular place, service, or event.
-
E.
operatesTouristAttraction
Indicates that an entity manages and runs the day-to-day operations of a tourist attraction.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a8459f88190a54cae4c8cb05119 |
completed | April 19, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:34 a.m.