Triple
T23473614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudolf V of Ruritania |
E570196
|
entity |
| Predicate | hasLookAlike |
P144124
|
FINISHED |
| Object | Rudolf Rassendyll |
—
|
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: Rudolf Rassendyll | Statement: [Rudolf V of Ruritania, hasLookAlike, Rudolf Rassendyll]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLookAlike Context triple: [Rudolf V of Ruritania, hasLookAlike, Rudolf Rassendyll]
-
A.
lessSimilarTo
Indicates that one entity is considered to share fewer similarities or a weaker resemblance with another entity compared to some reference or alternative.
-
B.
hasSimilarAttraction
Indicates that two entities experience or exert a comparable level or type of attraction toward something or each other.
-
C.
resembles
Indicates that one entity is similar in appearance, form, or characteristics to another.
-
D.
hasSimilarityTo
Indicates that one entity shares common characteristics, features, or qualities with another entity to a notable degree.
-
E.
hasDoppelganger
chosen
Indicates that an entity has a counterpart or double that closely resembles it, often in appearance, behavior, or role.
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a70363488190bcbdedec5c2a945c |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:58 p.m.