Triple

T9740103
Position Surface form Disambiguated ID Type / Status
Subject REYES architecture E236164 entity
Predicate visibilityComputation P90442 FINISHED
Object per-bucket hidden-surface determination 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: per-bucket hidden-surface determination | Statement: [REYES architecture, visibilityComputation, per-bucket hidden-surface determination]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: visibilityComputation
Context triple: [REYES architecture, visibilityComputation, per-bucket hidden-surface determination]
  • A. visibilityStatus
    Indicates the current level or state of how observable, accessible, or exposed an entity is within a given context.
  • B. visibleAt
    Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
  • C. visibleRemains
    Indicates that some physical remnants of an entity or event can still be seen or visually detected.
  • D. visibilityRequirement
    Indicates that one entity must be visible or perceivable under specified conditions for another entity, action, or rule to apply.
  • E. gainedVisibilityThrough
    Indicates that one entity became more visible, prominent, or well-known as a result of another entity or mechanism.
  • 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_69ca84d313e88190983ee6ffd0ef60d2 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9f29a5bc8190b2b391017405c71e completed April 1, 2026, 10:41 p.m.
PD Predicate disambiguation batch_69cd03cc128c81908b84ef224f858b4e completed April 1, 2026, 11:38 a.m.
PDg Predicate description generation batch_69cd06aa8bc88190904be19c8953def8 completed April 1, 2026, 11:51 a.m.
Created at: March 30, 2026, 8:22 p.m.