Triple
T32520471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deputy prime ministers of Belgium |
E831166
|
entity |
| Predicate | meetsInBody |
P117542
|
FINISHED |
| Object | inner cabinet |
—
|
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: inner cabinet | Statement: [Deputy prime ministers of Belgium, meetsInBody, inner cabinet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetsInBody Context triple: [Deputy prime ministers of Belgium, meetsInBody, inner cabinet]
-
A.
isInBody
Indicates that one entity is physically contained within or located inside the body of another entity.
-
B.
hasMeetingBody
chosen
Indicates that an entity (such as a meeting or event) is associated with a specific body or group that formally convenes or participates in that meeting.
-
C.
belongsToBody
Indicates that something is a part of, or under the ownership/authority of, a particular body or organization.
-
D.
locatedOnBody
Indicates that one entity is physically situated on the surface or external part of another entity’s body.
-
E.
meetsTo
Indicates that one entity comes together with another at a specific time and place for an encounter, appointment, or interaction.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c50e0e0081908a9b7775f6fa6484 |
completed | May 3, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1 a.m.