Triple

T15053300
Position Surface form Disambiguated ID Type / Status
Subject Davaar Island E379420 entity
Predicate hasAccessWarning P117142 FINISHED
Object causeway can be dangerous outside low tide 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: causeway can be dangerous outside low tide | Statement: [Davaar Island, hasAccessWarning, causeway can be dangerous outside low tide]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAccessWarning
Context triple: [Davaar Island, hasAccessWarning, causeway can be dangerous outside low tide]
  • A. hasHumanAccess
    Indicates that a human is able to access, use, or interact with the referenced entity or resource.
  • B. hasAccessTo
    Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
  • C. hasAccessException
    Indicates that a usual access rule or restriction is overridden or exempted for a particular entity or situation.
  • D. hasDisabledAccess
    Indicates that an entity provides facilities, features, or accommodations that make it accessible to people with disabilities.
  • E. hasAccessTowards
    Indicates that one entity possesses the ability, permission, or means to reach, use, or interact with another entity or resource.
  • 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_69d85cd64d108190853797a95c11cc45 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69deda92091c81909180f486edf01405 completed April 15, 2026, 12:23 a.m.
PD Predicate disambiguation batch_69deb95a182081908fffc4402b02a394 completed April 14, 2026, 10:02 p.m.
PDg Predicate description generation batch_69dec71e8dcc81908badc834b6ccf273 completed April 14, 2026, 11 p.m.
Created at: April 10, 2026, 3:01 a.m.