Triple

T13451595
Position Surface form Disambiguated ID Type / Status
Subject Lote Tree of the Utmost Boundary E320619 entity
Predicate beyondItExtendsOnly P53166 FINISHED
Object God’s knowledge 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: God’s knowledge | Statement: [Lote Tree of the Utmost Boundary, beyondItExtendsOnly, God’s knowledge]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: beyondItExtendsOnly
Context triple: [Lote Tree of the Utmost Boundary, beyondItExtendsOnly, God’s knowledge]
  • A. extendsBeyond chosen
    Indicates that one entity continues past or surpasses the spatial, temporal, or conceptual limits of another entity.
  • B. extendsTo
    Indicates that one entity reaches, stretches, or continues its scope, influence, or coverage up to or into another entity.
  • C. extendedFrom
    Indicates that one entity is derived by adding to or building upon the scope, content, or structure of another entity.
  • D. mayExtendTo
    Indicates that something has the potential or permission to reach, continue, or be applied up to a specified limit, scope, or boundary.
  • E. extendsBetween
    Indicates a relationship where one entity spans or stretches from one point, object, or boundary to another, covering the space between them.
  • 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_69d80761e6cc8190a90c844589998ecc completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbaefae85481909e6a59797cbb25e7 completed April 12, 2026, 2:40 p.m.
PD Predicate disambiguation batch_69d9a03ce03481908c61094f0cc0c158 completed April 11, 2026, 1:13 a.m.
Created at: April 9, 2026, 9:41 p.m.