Triple
T14030105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portrait of William III, Prince of Orange |
E337564
|
entity |
| Predicate | depictsFutureRole |
P52440
|
FINISHED |
| Object | King of England |
—
|
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: King of England | Statement: [Portrait of William III, Prince of Orange, depictsFutureRole, King of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictsFutureRole Context triple: [Portrait of William III, Prince of Orange, depictsFutureRole, King of England]
-
A.
depictsPersonRole
Indicates that an image or representation shows a person in a specific role, function, or capacity.
-
B.
characterFutureRole
chosen
Indicates the role or position that a character is expected or intended to assume at a later point in time.
-
C.
destinedRole
Indicates that an entity is assigned or fated to fulfill a particular role or function, typically in a future or predetermined context.
-
D.
plannedRole
Indicates that an entity is expected or intended to assume a particular role or function in a planned or future context.
-
E.
depicts
Indicates that one entity visually represents, portrays, or shows another entity.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2fa9f8248190930954d609dee5f1 |
completed | April 14, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.