Triple
T23686510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fries Museum |
E585181
|
entity |
| Predicate | visitorOrientation |
P153382
|
FINISHED |
| Object | regional visitors |
—
|
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: regional visitors | Statement: [Fries Museum, visitorOrientation, regional visitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitorOrientation Context triple: [Fries Museum, visitorOrientation, regional visitors]
-
A.
visitorInformation
Indicates that information or details are provided for or about visitors in relation to a particular place, service, or event.
-
B.
visitorCenter
Indicates that a location serves as a visitor center for a place, providing information or services to visitors of that place.
-
C.
visitorGuideline
Indicates guidelines or rules that specify how visitors are expected or allowed to behave or proceed in a particular context.
-
D.
visitorService
Indicates a relationship where a service is provided specifically for or to visitors, such as assistance, information, or support during their visit.
-
E.
visitorPractice
Indicates that a visitor engages in or performs a particular practice, activity, or routine.
- 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b5bf1c10819085d48c4225cc63fc |
completed | April 29, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f157cc43a881909ed2d8b0a09b5d73 |
completed | April 29, 2026, 12:58 a.m. |
Created at: April 17, 2026, 6:52 p.m.