Triple
T35453297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown Princess of Prussia |
E1024697
|
entity |
| Predicate | expectedFutureRole |
P21890
|
FINISHED |
| Object | future Queen consort of Prussia |
—
|
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: future Queen consort of Prussia | Statement: [Crown Princess of Prussia, expectedFutureRole, future Queen consort of Prussia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expectedFutureRole Context triple: [Crown Princess of Prussia, expectedFutureRole, future Queen consort of Prussia]
-
A.
destinedRole
Indicates that an entity is assigned or fated to fulfill a particular role or function, typically in a future or predetermined context.
-
B.
plannedRole
chosen
Indicates that an entity is expected or intended to assume a particular role or function in a planned or future context.
-
C.
characterFutureRole
Indicates the role or position that a character is expected or intended to assume at a later point in time.
-
D.
possibleRole
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
-
E.
subsequentRole
Indicates that one role or position is held after, and in succession to, another role or position.
- 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_69f76df92f108190817222e520e22268 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.