Triple
T25157230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harlequin Valentine |
E626346
|
entity |
| Predicate | hasMythologicalCharacter |
P86125
|
FINISHED |
| Object | Harlequin |
—
|
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: Harlequin | Statement: [Harlequin Valentine, hasMythologicalCharacter, Harlequin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMythologicalCharacter Context triple: [Harlequin Valentine, hasMythologicalCharacter, Harlequin]
-
A.
hasMythologicalNamesake
Indicates that one entity is named after, or shares its name with, a figure or element from mythology.
-
B.
hasMythologicalFeature
Indicates that an entity possesses a characteristic, attribute, or element derived from mythology or mythological beings.
-
C.
hasMythicalFigure
chosen
Indicates that one entity is associated with, features, or includes a particular mythical or legendary figure.
-
D.
isMythologicalFigureType
Indicates that one entity is classified as a specific type or category of mythological figure in relation to another entity.
-
E.
hasMythologicalBearer
Indicates that something is associated with, carried by, or represented by a figure from mythology.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 18, 2026, 6:30 a.m.