Triple
T35914244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sieve Portrait |
E1038700
|
entity |
| Predicate | portraysDynasty |
P95471
|
FINISHED |
| Object | House of Tudor |
—
|
NE NERFINISHED |
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: House of Tudor | Statement: [Sieve Portrait, portraysDynasty, House of Tudor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portraysDynasty Context triple: [Sieve Portrait, portraysDynasty, House of Tudor]
-
A.
depictsDynasty
chosen
Indicates that one entity visually represents or portrays a particular dynasty.
-
B.
formedDynasty
Indicates that an entity established or created a ruling dynasty.
-
C.
dynasty
Indicates a hereditary ruling line or family that holds power over a state or territory across successive generations.
-
D.
dynastyProvided
Indicates that a particular dynasty supplied, supported, or was responsible for providing something to another entity or context.
-
E.
traditionalDynasty
Indicates a relationship where a dynasty is recognized as traditional, typically long-established and rooted in customary or historical authority.
- 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_69f76e2320748190b7f5c4750d0cd0d3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff6074bcd4819090b72cd6209ff206 |
completed | May 9, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69ff600aba888190812a6e7eca0283b8 |
completed | May 9, 2026, 4:25 p.m. |
Created at: May 3, 2026, 4:07 p.m.