Triple
T31359281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dulcinea del Toboso |
E799819
|
entity |
| Predicate | realNameInFiction |
P9233
|
FINISHED |
| Object | Aldonza Lorenzo |
—
|
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: Aldonza Lorenzo | Statement: [Dulcinea del Toboso, realNameInFiction, Aldonza Lorenzo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realNameInFiction Context triple: [Dulcinea del Toboso, realNameInFiction, Aldonza Lorenzo]
-
A.
fictionalBirthName
Indicates the original personal name assigned to a fictional character at birth, as distinct from any later or alternate names they may use.
-
B.
realName
chosen
Indicates that one entity is the actual, full, or birth name of another entity, which may be known by an alias, nickname, or alternate identity.
-
C.
fictionalNameInSeries
Indicates that a fictional character is known by a particular name within a specific narrative series or franchise.
-
D.
hasFictionalAlias
Indicates that an entity is known by an alternative name or identity within a fictional context.
-
E.
isGivenNameOfFictionalCharacter
Indicates that a given name is the personal name borne by a fictional character.
- 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f4a00ac8190b7d9fa66781cef1f |
completed | May 3, 2026, 1:05 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:17 p.m.