Triple

T6921120
Position Surface form Disambiguated ID Type / Status
Subject Neque semper arcum tendit Apollo E160186 entity
Predicate impliedMeaning P10718 FINISHED
Object One should not work all the time 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: One should not work all the time | Statement: [Neque semper arcum tendit Apollo, impliedMeaning, One should not work all the time]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: impliedMeaning
Context triple: [Neque semper arcum tendit Apollo, impliedMeaning, One should not work all the time]
  • A. possibleMeaning chosen
    Indicates that something may plausibly represent, signify, or be interpreted as a particular meaning or sense.
  • B. intendedInterpretation
    Indicates that one entity is meant to be understood or interpreted in a particular way, sense, or meaning relative to another.
  • C. logicalMeaning
    Indicates that one entity expresses, encodes, or conveys the logical content, implication, or formal meaning of another.
  • D. commonMeaning
    Indicates that multiple entities share the same or very similar meaning or semantic 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_69c6884d350081908d8a970e4d40ad78 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6d9fb8ac48190b50bbc47fad8288f completed March 27, 2026, 7:26 p.m.
PD Predicate disambiguation batch_69c6d7b93d688190a297244ce81b67ac completed March 27, 2026, 7:17 p.m.
Created at: March 27, 2026, 2:26 p.m.