Triple

T31908248
Position Surface form Disambiguated ID Type / Status
Subject Tianming E814612 entity
Predicate hasEpistemicSign P143137 FINISHED
Object omens and portents 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: omens and portents | Statement: [Tianming, hasEpistemicSign, omens and portents]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEpistemicSign
Context triple: [Tianming, hasEpistemicSign, omens and portents]
  • A. epistemicCondition
    Indicates that one situation or proposition holds only under certain knowledge, belief, or informational conditions related to another.
  • B. usesEpistemicMeans
    Indicates that an agent employs knowledge-related methods, reasoning, or informational tools as the means to carry out or support an action or relationship.
  • C. epistemicAttitude
    Indicates the type or stance of a subject’s knowledge, belief, or certainty toward a proposition or statement.
  • D. epistemicBasis chosen
    Indicates the justificatory relationship by which one piece of information, belief, or evidence serves as the basis for holding another belief or knowledge claim.
  • E. epistemicStatus
    Indicates the degree of certainty, justification, or knowledge an agent has regarding a particular proposition or claim.
  • 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_69f348f109d88190b5005372c53d2fcd completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6b1b6a1f08190b1d5306ae35977cb completed May 3, 2026, 2:23 a.m.
PD Predicate disambiguation batch_69f6aca59d4881908d14ed47962703bd completed May 3, 2026, 2:02 a.m.
Created at: May 1, 2026, 12:01 a.m.