Triple
T10041948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ministry of Defence (Sweden) |
E205315
|
entity |
| Predicate | hasMinisterialTitle |
P7410
|
FINISHED |
| Object | Minister for Defence |
—
|
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: Minister for Defence | Statement: [Ministry of Defence (Sweden), hasMinisterialTitle, Minister for Defence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMinisterialTitle Context triple: [Ministry of Defence (Sweden), hasMinisterialTitle, Minister for Defence]
-
A.
hasMinisterTitle
chosen
Indicates that an entity holds or is associated with a specific ministerial title or office.
-
B.
hasMinisterialRank
Indicates that an entity holds a position or status equivalent to a government minister in rank.
-
C.
hasMinister
Indicates that one entity serves as the minister (political, religious, or administrative official) responsible for or associated with another entity.
-
D.
hadMinisterialPost
Indicates that an entity has held or occupied a ministerial government position or office.
-
E.
hasMinisterialSeat
Indicates that a governmental or administrative body holds its official ministerial seat or headquarters at a particular location.
- 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcee48d8c8190af7c93b60f8ca7cb |
completed | April 2, 2026, 2:05 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:55 p.m.