Triple
T36024257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rijksmonuments in South Holland |
E1042079
|
entity |
| Predicate | hasOnlineList |
P9162
|
FINISHED |
| Object | Rijksmonument register website |
—
|
NE NERFINISHED |
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: Rijksmonument register website | Statement: [Rijksmonuments in South Holland, hasOnlineList, Rijksmonument register website]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnlineList Context triple: [Rijksmonuments in South Holland, hasOnlineList, Rijksmonument register website]
-
A.
isAvailableOnline
Indicates that something can be accessed or obtained via the internet.
-
B.
isOnLine
Indicates that one entity is located directly along, or in contact with, a specified line or linear path.
-
C.
hasOnlineRequirement
Indicates that an entity must be accessed, completed, or fulfilled through an online or internet-based component.
-
D.
hasOnlineCatalog
chosen
Indicates that an entity provides a catalog of its items or offerings that is accessible via the internet.
-
E.
hasOnlineSessions
Indicates that an entity conducts or offers sessions, meetings, or activities via the internet rather than solely in person.
- 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_69f76e2c568881909e1e21f85252b0f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:07 p.m.