Triple
T15868912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koutsovlachs |
E384781
|
entity |
| Predicate | hasNuance |
P120839
|
FINISHED |
| Object | often derogatory |
—
|
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: often derogatory | Statement: [Koutsovlachs, hasNuance, often derogatory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNuance Context triple: [Koutsovlachs, hasNuance, often derogatory]
-
A.
hasVoiceIn
Indicates that an entity participates by providing a voice role or vocal performance in another entity, such as a work, production, or recording.
-
B.
hasSpeechFluency
Indicates that an entity exhibits a certain level or quality of smoothness, coherence, and ease in spoken language production.
-
C.
haveRichVoiceSystem
Indicates that an entity possesses a voice system characterized by richness, such as depth, fullness, or expressive quality.
-
D.
hasVoices
Indicates that an entity possesses or includes one or more vocal parts, voice tracks, or spoken/sung voice elements.
-
E.
hasVoiceSystem
Indicates that one entity possesses or is equipped with a particular voice-based system or voice technology.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142b976c081908d3ba3e705419f3a |
completed | April 16, 2026, 8:12 p.m. |
| PDg | Predicate description generation | batch_69e174da2c2c819099ec46616798245a |
completed | April 16, 2026, 11:46 p.m. |
Created at: April 10, 2026, 4:50 a.m.