Triple
T14436470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agentschap van het Rijk |
E357975
|
entity |
| Predicate | typicalTasks |
P107993
|
FINISHED |
| Object | management of national infrastructure |
—
|
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: management of national infrastructure | Statement: [Agentschap van het Rijk, typicalTasks, management of national infrastructure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTasks Context triple: [Agentschap van het Rijk, typicalTasks, management of national infrastructure]
-
A.
typicalTask
chosen
Indicates the kind of task or activity that is normally or characteristically performed by an entity.
-
B.
taskType
Indicates the specific category or kind of task an action or assignment belongs to within a broader set of tasks.
-
C.
userTask
Indicates that a specific task is assigned to, owned by, or performed by a particular user.
-
D.
typicalWorkflow
Indicates that one process, sequence, or set of actions represents the standard or commonly followed way of performing a task or achieving a goal.
-
E.
canTask
Indicates that an entity has the ability or permission to perform a specified task.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9148cf4481909082cc91b2f76218 |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.