Triple
T31824314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Les Pyjamasques |
E812348
|
entity |
| Predicate | hasOriginalCharacterName |
P194760
|
FINISHED |
| Object | Yoyo |
—
|
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: Yoyo | Statement: [Les Pyjamasques, hasOriginalCharacterName, Yoyo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalCharacterName Context triple: [Les Pyjamasques, hasOriginalCharacterName, Yoyo]
-
A.
hasOriginalCharacter
Indicates that an entity includes, features, or is associated with an original character distinct from pre-existing or canonical characters.
-
B.
hasOriginalNameOf
Indicates that one entity is the original or earlier name from which another entity’s current or later name is derived.
-
C.
hasUncertainOriginalName
Indicates that the entity’s original name is not known with certainty or is subject to doubt or ambiguity.
-
D.
hasOriginalCharacterOwner
Indicates that an entity is the original owner or creator of a given character.
-
E.
hasCharacterNamedAfter
Indicates that one entity has a character whose name is derived from or intentionally based on another entity.
- F. None of above. chosen
Provenance (4 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_69f348e97fa48190aa06286962af6dee |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
| PDg | Predicate description generation | batch_69fd8640e1d4819081c98f15eeb221ab |
completed | May 8, 2026, 6:44 a.m. |
Created at: April 30, 2026, 11:46 p.m.