Triple

T11663646
Position Surface form Disambiguated ID Type / Status
Subject Os Cus de Judas E277187 entity
Predicate titleFigurativeMeaning P72897 FINISHED
Object remote and forsaken place 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: remote and forsaken place | Statement: [Os Cus de Judas, titleFigurativeMeaning, remote and forsaken place]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: titleFigurativeMeaning
Context triple: [Os Cus de Judas, titleFigurativeMeaning, remote and forsaken place]
  • A. figurativeMeaning
    Indicates that one entity is used in a non-literal, metaphorical, or symbolic sense to convey a meaning about another entity or concept.
  • B. titleMetaphor chosen
    Indicates that the title of a work functions metaphorically, expressing a figurative or symbolic meaning rather than a literal one.
  • C. logicalMeaning
    Indicates that one entity expresses, encodes, or conveys the logical content, implication, or formal meaning of another.
  • D. literalMeaningApproximation
    Indicates that one entity expresses an approximate or rough literal meaning of another entity, rather than an exact or fully precise interpretation.
  • E. stringMeaning
    Indicates that one entity represents the semantic content or interpretation of a given string associated 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_69d6aafd0a448190b44da30af8c6c519 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a3d3a64c819099f398ea22c8c180 completed April 10, 2026, 7:16 a.m.
PD Predicate disambiguation batch_69d88a73f9ac819095662042804bf40a completed April 10, 2026, 5:28 a.m.
Created at: April 8, 2026, 9:39 p.m.