Triple
T31791555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rijksmonument |
E811479
|
entity |
| Predicate | mayQualifyFor |
P106510
|
FINISHED |
| Object | restoration subsidies |
—
|
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: restoration subsidies | Statement: [rijksmonument, mayQualifyFor, restoration subsidies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayQualifyFor Context triple: [rijksmonument, mayQualifyFor, restoration subsidies]
-
A.
qualifyingFor
chosen
Indicates that one entity meets the necessary conditions or criteria to be eligible for another entity, status, or action.
-
B.
mayHoldQualification
Indicates that an entity is permitted or able to possess a particular qualification, certification, or credential.
-
C.
hasQualifying
Indicates that one entity possesses or meets a specific condition, attribute, or criterion that qualifies it in relation to another entity or context.
-
D.
mayApply
Indicates that an entity is permitted or eligible to submit or use something (such as a rule, action, or resource) under certain conditions.
-
E.
hasQualification
Indicates that an entity possesses a specific qualification, credential, or competency.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ac193ba881909883414161b0d7bb |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa21f2508190a204a424ffc00ca6 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:39 p.m.