Triple
T33925963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humbert Humbert |
E869751
|
entity |
| Predicate | selfDescriptionTerm |
P21265
|
FINISHED |
| Object | nympholept |
—
|
LITERAL FINISHED |
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: nympholept | Statement: [Humbert Humbert, selfDescriptionTerm, nympholept]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selfDescriptionTerm Context triple: [Humbert Humbert, selfDescriptionTerm, nympholept]
-
A.
symbolDescription
Indicates that a symbol is associated with or defined by a particular descriptive explanation or meaning.
-
B.
originatedFromSelfDescriptionBy
Indicates that something is derived from, based on, or produced by an entity’s own self-description.
-
C.
describedFrom
Indicates that something is characterized, explained, or defined based on information, perspective, or features originating from a particular source or reference point.
-
D.
isFrequentlyDescribedAs
chosen
Indicates that something is often characterized or referred to using a particular description or set of attributes.
-
E.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
- 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.