Triple
T223060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rijksmuseum |
E4257
|
entity |
| Predicate | visitorCountRecord |
P427
|
FINISHED |
| Object | over 2 million visitors per year |
—
|
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: over 2 million visitors per year | Statement: [Rijksmuseum, visitorCountRecord, over 2 million visitors per year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitorCountRecord Context triple: [Rijksmuseum, visitorCountRecord, over 2 million visitors per year]
-
A.
visitorCount
chosen
Indicates the number of visitors associated with a particular entity, context, or time period.
-
B.
sessionCount
Indicates the number of distinct sessions associated with an entity or interaction context.
-
C.
visitedBy
Indicates that a location or entity is the destination or target of a visit performed by another entity.
-
D.
frequentlyVisitedBy
Indicates that an entity is regularly or often visited by another entity.
-
E.
visitorCenter
Indicates that a location serves as a visitor center for a place, providing information or services to visitors of that place.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c705fd88190bfee7f5e1f7cee17 |
completed | Feb. 28, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69a25b5617788190814358aee3f7ae37 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.