Triple
T18119998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ministry of Food |
E433705
|
entity |
| Predicate | typeOfRationingManaged |
P130523
|
FINISHED |
| Object | civilian food rationing |
—
|
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: civilian food rationing | Statement: [Ministry of Food, typeOfRationingManaged, civilian food rationing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRationingManaged Context triple: [Ministry of Food, typeOfRationingManaged, civilian food rationing]
-
A.
typeOfPropertyManaged
Indicates the specific category or kind of property that an entity is responsible for managing.
-
B.
typeOfGrantManaged
Indicates that one entity manages or administers a specific type or category of grant in relation to another entity or context.
-
C.
classificationTypeManaged
Indicates that the classification type is controlled or administered through a managed process or system rather than being assigned freely or ad hoc.
-
D.
hasTypeOfManagement
Indicates that an entity is associated with or operates under a specified form or style of management.
-
E.
isManaged
Indicates that one entity exercises supervisory or administrative control over another entity.
- F. None of above. chosen
Provenance (4 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd9b21c81908d23b8d9840410df |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:28 a.m.