Triple
T4113642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senate House State Historic Site |
E90236
|
entity |
| Predicate | visitorInformation |
P54718
|
FINISHED |
| Object | offers guided tours |
—
|
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: offers guided tours | Statement: [Senate House State Historic Site, visitorInformation, offers guided tours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitorInformation Context triple: [Senate House State Historic Site, visitorInformation, offers guided tours]
-
A.
visitorCenter
Indicates that a location serves as a visitor center for a place, providing information or services to visitors of that place.
-
B.
visitorProfile
Indicates a relationship where a profile encapsulates information or attributes associated with a particular visitor.
-
C.
visitorStatus
Indicates the current state or condition of an entity in its role as a visitor (e.g., whether they are active, pending, past, or otherwise classified in their visit).
-
D.
visitorUse
Indicates that an entity is being used, accessed, or engaged with by a visitor or temporary user.
-
E.
touristAccess
Indicates that a place or resource is available for use or visitation by tourists.
- F. None of above. chosen
Provenance (4 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_69aed95c080881908125e30c5dcdc6f8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03d7240c8190a64dcbc669772808 |
completed | March 9, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69af0183eb84819087d7184de28f5514 |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af03d5cce88190ad53bc6cfe10b21e |
completed | March 9, 2026, 5:31 p.m. |
Created at: March 9, 2026, 3:41 p.m.