Triple
T31433252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Promenade des Gouverneurs |
E801851
|
entity |
| Predicate | hasTouristInformationPanels |
P51898
|
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: [Promenade des Gouverneurs, hasTouristInformationPanels, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTouristInformationPanels Context triple: [Promenade des Gouverneurs, hasTouristInformationPanels, yes]
-
A.
hasTourismInformationCenter
Indicates that a place or area contains or is served by a tourism information center providing guidance and services to visitors.
-
B.
hasTouristSignage
chosen
Indicates that there is official signage present to guide or inform tourists about a place, route, or attraction.
-
C.
tourInformation
Indicates that an entity provides details or data about a tour, such as schedule, itinerary, or features.
-
D.
hasTouristInfrastructure
Indicates that a place is equipped with facilities and services designed to support and accommodate tourists.
-
E.
hasGoalForTourists
Indicates that something is intended or designed to achieve a specific objective or benefit for tourists.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 30, 2026, 8:59 p.m.