Triple
T16280410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown Prince of Sweden |
E395247
|
entity |
| Predicate | preparesForRoleAs |
P74372
|
FINISHED |
| Object | head of state 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: head of state of Sweden | Statement: [Crown Prince of Sweden, preparesForRoleAs, head of state of Sweden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preparesForRoleAs Context triple: [Crown Prince of Sweden, preparesForRoleAs, head of state of Sweden]
-
A.
preparesFor
Indicates that one entity is used, designed, or undertaken in order to get another entity ready for a future event, state, or activity.
-
B.
preparesWith
Indicates that one entity is used as a means, tool, or method by which another entity is prepared or made ready.
-
C.
preparatoryRole
chosen
Indicates that one entity performs a function or activity that serves as preparation or groundwork for another entity, event, or process.
-
D.
preparedFor
Indicates that one entity has been made ready, equipped, or arranged in anticipation of use by or in connection with another entity.
-
E.
preparesForEvent
Indicates that one entity performs actions or makes arrangements in anticipation of a specific event.
- 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.