Triple

T11449807
Position Surface form Disambiguated ID Type / Status
Subject Terumat HaDeshen E271364 entity
Predicate hasApproximateNumberOfResponsa P99635 FINISHED
Object around 300 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: around 300 | Statement: [Terumat HaDeshen, hasApproximateNumberOfResponsa, around 300]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasApproximateNumberOfResponsa
Context triple: [Terumat HaDeshen, hasApproximateNumberOfResponsa, around 300]
  • A. holdsApproximatelyFor
    Indicates that a condition, relation, or value is valid only to an approximate degree or within a tolerance, rather than holding exactly.
  • B. hasApproximateUse
    Indicates that one entity is used for a purpose that is similar to, but not exactly the same as, the use or function of another entity.
  • C. mineCountApproximate
    Indicates that the number of mines associated with an entity is estimated or roughly counted rather than known exactly.
  • D. hasApproximateNumberOfLetters
    Indicates that an entity is associated with a number that roughly, but not exactly, corresponds to the count of letters it contains.
  • E. hasNumberOfCasesApprox
    Indicates that an entity is associated with an approximate (not exact) count of cases.
  • 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_69d6aadff8888190a13f253f0d460874 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d822f2138081909408c7916cef99c9 completed April 9, 2026, 10:06 p.m.
PD Predicate disambiguation batch_69d80867ff248190bb157fa9e355353b completed April 9, 2026, 8:13 p.m.
PDg Predicate description generation batch_69d822ef46988190a1c360da4ee14fef completed April 9, 2026, 10:06 p.m.
Created at: April 8, 2026, 9:35 p.m.