Triple

T15211126
Position Surface form Disambiguated ID Type / Status
Subject The Invisible Man (2020 film) E363515 entity
Predicate invisibilityExplainedBy P117134 FINISHED
Object advanced optics suit 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: advanced optics suit | Statement: [The Invisible Man (2020 film), invisibilityExplainedBy, advanced optics suit]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: invisibilityExplainedBy
Context triple: [The Invisible Man (2020 film), invisibilityExplainedBy, advanced optics suit]
  • A. visibilityReason
    Indicates the reason or cause for why something is visible or has become visible in a given context.
  • B. visibleUnder
    Indicates that one entity can be seen or perceived when another specified condition, context, or covering entity is present or in effect.
  • C. surfaceNotVisibleInVisibleLight
    Indicates that the surface of an entity cannot be seen or detected when using visible light.
  • D. identityConcealedBy
    Indicates that one entity hides, masks, or obscures the true identity of another entity.
  • E. hiddenIn
    Indicates that one entity is concealed within, behind, or inside another entity so that it is not readily visible or apparent.
  • 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0076ad4ec81908d36f541fca08d72 completed April 15, 2026, 9:47 p.m.
PD Predicate disambiguation batch_69deb97ee9d881908711dbe12a55283c completed April 14, 2026, 10:02 p.m.
PDg Predicate description generation batch_69dec72059c08190a34f513a00185b08 completed April 14, 2026, 11 p.m.
Created at: April 10, 2026, 3:11 a.m.