Triple
T6952989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anatomical Theatre of Padua |
E160971
|
entity |
| Predicate | hasVisitorInformation |
P54718
|
FINISHED |
| Object | guided tours available |
—
|
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: guided tours available | Statement: [Anatomical Theatre of Padua, hasVisitorInformation, guided tours available]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisitorInformation Context triple: [Anatomical Theatre of Padua, hasVisitorInformation, guided tours available]
-
A.
hasVisitorPolicy
Indicates that an entity has an established policy governing the presence, behavior, or permissions of visitors.
-
B.
visitorInformation
chosen
Indicates that information or details are provided for or about visitors in relation to a particular place, service, or event.
-
C.
hasVisitation
Indicates that one entity visits, or is allowed or scheduled to visit, another entity or location.
-
D.
hasVisitorType
Indicates the type or category of visitor associated with an entity (e.g., guest, customer, tourist, patient).
-
E.
hasVisitorServices
Indicates that an entity provides services or facilities specifically intended for visitors or guests.
- 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_69c68850419081909fb426b8f5a304c7 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dacca12481908942ba793a104cc3 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bf0a7c8190b5ed4aca22ba9b97 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:29 p.m.