Triple

T2157725
Position Surface form Disambiguated ID Type / Status
Subject Gutenberg Bible copies E47929 entity
Predicate areValuedFor P21633 FINISHED
Object historical significance 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: historical significance | Statement: [Gutenberg Bible copies, areValuedFor, historical significance]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: areValuedFor
Context triple: [Gutenberg Bible copies, areValuedFor, historical significance]
  • A. isValuedFor chosen
    Indicates that one entity is appreciated, esteemed, or considered important because of a particular quality, contribution, or characteristic it provides to another entity.
  • B. valuedBy
    Indicates that one entity is regarded as important, useful, or held in high esteem by another entity.
  • C. value
    Indicates that one entity possesses, represents, or corresponds to a particular quantity, quality, or assigned worth.
  • D. supportsValue
    Indicates that one entity provides justification, evidence, or backing for the truth, relevance, or appropriateness of a particular value associated with another entity.
  • E. isValuePriced
    Indicates that something is offered at a relatively low or favorable price compared to typical or premium alternatives.
  • 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_69a88a1d1fd8819088b34990d69a712f completed March 4, 2026, 7:38 p.m.
NER Named-entity recognition batch_69abbe68fe0c8190beb5db003738a6e5 completed March 7, 2026, 5:58 a.m.
PD Predicate disambiguation batch_69abbd9a60648190b20b116be5c7ad98 completed March 7, 2026, 5:54 a.m.
Created at: March 4, 2026, 7:44 p.m.