Triple
T8362192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ridderzaal |
E197033
|
entity |
| Predicate | openingOfParliamentVenueFor |
P65421
|
FINISHED |
| Object | Dutch monarch |
—
|
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: Dutch monarch | Statement: [Ridderzaal, openingOfParliamentVenueFor, Dutch monarch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingOfParliamentVenueFor Context triple: [Ridderzaal, openingOfParliamentVenueFor, Dutch monarch]
-
A.
parliamentLocation
Indicates the place where a country's or region's parliament is situated or convenes.
-
B.
inauguralVenue
chosen
Indicates the location or facility where an event, organization, or activity was first officially launched or held.
-
C.
officeHeldIn
Indicates that a particular office or position is held within or associated with a specific geographic or administrative location.
-
D.
capitalOfMeetingPlace
Indicates that a location serves as the capital city where a particular meeting or set of meetings takes place.
-
E.
parliamentaryHouse
Indicates that one entity functions as a parliamentary chamber or house within the legislative system of another entity.
- 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_69ca82f2dbe48190aba982e75a0d94de |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb8074e4588190b394d1622adca2cb |
completed | March 31, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6 p.m.