Triple

T35539664
Position Surface form Disambiguated ID Type / Status
Subject Scavi E1027025 entity
Predicate safetyConstraint P20206 FINISHED
Object not suitable for people with severe claustrophobia 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: not suitable for people with severe claustrophobia | Statement: [Scavi, safetyConstraint, not suitable for people with severe claustrophobia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: safetyConstraint
Context triple: [Scavi, safetyConstraint, not suitable for people with severe claustrophobia]
  • A. safetyRequirement chosen
    Indicates that one entity specifies or imposes conditions, standards, or measures necessary to ensure the safety of another entity or activity.
  • B. safetyGoal
    Indicates that an entity is associated with a specific safety objective or target condition intended to prevent harm or reduce risk.
  • C. safetyContext
    Indicates the circumstances, conditions, or environment that affect how safe an action, object, or situation is.
  • D. safetyConcept
    Indicates that something embodies, represents, or is associated with a principle, idea, or framework related to safety.
  • E. safety
    Indicates that an entity provides, ensures, or is associated with protection from harm, danger, or risk for another entity or within a given context.
  • 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_69f76e008ba08190927acd8e5e0344c8 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79ec355048190af30123ceb6efa2b completed May 3, 2026, 7:15 p.m.
PD Predicate disambiguation batch_69f79e4bdbcc8190be7a0d2cf8a77b64 completed May 3, 2026, 7:13 p.m.
Created at: May 3, 2026, 4:04 p.m.