Triple
T16280391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown Prince of Sweden |
E395247
|
entity |
| Predicate | preparedForRoleAs |
P2534
|
FINISHED |
| Object | constitutional monarch of Sweden |
—
|
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: constitutional monarch of Sweden | Statement: [Crown Prince of Sweden, preparedForRoleAs, constitutional monarch of Sweden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preparedForRoleAs Context triple: [Crown Prince of Sweden, preparedForRoleAs, constitutional monarch of Sweden]
-
A.
preparedFor
Indicates that one entity has been made ready, equipped, or arranged in anticipation of use by or in connection with another entity.
-
B.
preparesFor
chosen
Indicates that one entity is used, designed, or undertaken in order to get another entity ready for a future event, state, or activity.
-
C.
preparedBefore
Indicates that one entity was prepared or made ready at an earlier time than another entity.
-
D.
preparatoryRole
Indicates that one entity performs a function or activity that serves as preparation or groundwork for another entity, event, or process.
-
E.
preparedAt
Indicates the time or place at which something was prepared or made ready.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24611926c81909b276ca3f406f15d |
completed | April 17, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.