Triple

T17486965
Position Surface form Disambiguated ID Type / Status
Subject Peircean semiotics E425800 entity
Predicate classifiesSignByRelationToInterpretant P127647 FINISHED
Object rheme 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: rheme | Statement: [Peircean semiotics, classifiesSignByRelationToInterpretant, rheme]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: classifiesSignByRelationToInterpretant
Context triple: [Peircean semiotics, classifiesSignByRelationToInterpretant, rheme]
  • A. signInterpretation
    Indicates that one entity provides or assigns a particular meaning, explanation, or reading to a given sign, symbol, or signal.
  • B. hasSymbolicInterpretation
    Indicates that one entity is understood or used as a symbolic representation or metaphorical stand-in for another entity or concept.
  • C. symbolicRelation
    Indicates a relationship where one entity stands for, represents, or conveys meaning about another through symbols or abstract signs.
  • D. definesClassification
    Indicates that one entity specifies or establishes the classification or category to which another entity belongs.
  • E. definesRelationshipBetween
    Indicates that one entity specifies or establishes the nature, type, or rules of a relationship that exists between two or more other entities.
  • 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_69d889dccf7481909264a1844a2e9100 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e451d2a5208190b25944626e779fdc completed April 19, 2026, 3:53 a.m.
PD Predicate disambiguation batch_69e3b4f341c88190adabe526d8903b05 completed April 18, 2026, 4:44 p.m.
PDg Predicate description generation batch_69e3bbb37d148190b7f38599c06594ee completed April 18, 2026, 5:13 p.m.
Created at: April 10, 2026, 5:48 a.m.