Triple
T37455768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destroyer |
E930794
|
entity |
| Predicate | contrastsWithClass |
P107167
|
FINISHED |
| Object | Alchemist |
—
|
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: Alchemist | Statement: [Destroyer, contrastsWithClass, Alchemist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contrastsWithClass Context triple: [Destroyer, contrastsWithClass, Alchemist]
-
A.
providesContrastWith
Indicates that one entity is used to highlight differences or distinctions when compared with another entity.
-
B.
socialClassContrastWith
Indicates a contrast or difference between the social classes or social standings associated with two entities.
-
C.
contrastedWithObject
chosen
Indicates that one entity is explicitly compared to another by highlighting their differences or opposing characteristics.
-
D.
initiallyContrastsWith
Indicates that one entity is first presented or perceived in opposition or contrast to another entity at the beginning of a sequence, process, or context.
-
E.
dramaticContrastWith
Indicates that one entity is presented in a way that sharply emphasizes differences in tone, style, or impact when compared with 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff370698ec81909bb1596d7d4112ba |
completed | May 9, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69ff3699b6288190b564839cb05f5cf6 |
completed | May 9, 2026, 1:28 p.m. |
Created at: May 3, 2026, 4:17 p.m.