Triple
T26828534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algernon Moncrieff |
E675433
|
entity |
| Predicate | usesAliasOfAnotherCharacter |
P41555
|
FINISHED |
| Object | Ernest |
—
|
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: Ernest | Statement: [Algernon Moncrieff, usesAliasOfAnotherCharacter, Ernest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAliasOfAnotherCharacter Context triple: [Algernon Moncrieff, usesAliasOfAnotherCharacter, Ernest]
-
A.
hasFictionalAlterEgoOf
Indicates that one entity is the fictional alter ego, persona, or alternate identity of another entity.
-
B.
hasFictionalAlias
Indicates that an entity is known by an alternative name or identity within a fictional context.
-
C.
associatedWithCharacterAlias
Indicates that one entity is linked to or connected with an alternative name or alias used for a particular character.
-
D.
characterAlias
chosen
Indicates that one character is known or referred to by an alternative name or alias.
-
E.
namedAfterFictionalCharacter
Indicates that one entity has been given its name in honor of, or derived from, 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 5 a.m.