Triple
T20186935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fainting Fancies |
E492885
|
entity |
| Predicate | hasComplement |
P78551
|
FINISHED |
| Object | reviving sweet |
—
|
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: reviving sweet | Statement: [Fainting Fancies, hasComplement, reviving sweet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComplement Context triple: [Fainting Fancies, hasComplement, reviving sweet]
-
A.
requiresComplement
Indicates that one entity depends on another entity as a necessary complement to be complete, functional, or valid.
-
B.
hasComplementaryColor
Indicates that one color is the complementary (i.e., opposite on the color wheel, providing maximum contrast) counterpart of another color.
-
C.
complementOf
Indicates that one entity serves as a complement to another, completing or specifying it in a grammatical or semantic relationship.
-
D.
complement
chosen
Indicates that one entity completes, enhances, or makes another entity whole or more effective by providing what it lacks.
-
E.
hasSupplement
Indicates that one entity provides or is associated with an additional supporting or enhancing item, resource, or component for another entity.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad143c48190b9d52c331e8101d6 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:36 p.m.