Triple

T3104558
Position Surface form Disambiguated ID Type / Status
Subject post exchange E64799 entity
Predicate hasAccessRestrictedTo P8521 FINISHED
Object authorized patrons 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: authorized patrons | Statement: [post exchange, hasAccessRestrictedTo, authorized patrons]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAccessRestrictedTo
Context triple: [post exchange, hasAccessRestrictedTo, authorized patrons]
  • A. accessRestrictedTo chosen
    Indicates that access to a resource, location, or information is limited exclusively to a specified entity or group under defined conditions.
  • B. accessRestriction
    Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
  • C. hasAccessTo
    Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
  • D. hasAccessTowards
    Indicates that one entity possesses the ability, permission, or means to reach, use, or interact with another entity or resource.
  • E. hasLimitedAuthorityOver
    Indicates that one entity holds a constrained or partial power to direct, control, or make decisions about another entity, but not full or unrestricted authority.
  • 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_69ad857eeaf48190b34ebfdaa7a264cf completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada29a90e88190afb8a10291ef1946 completed March 8, 2026, 4:23 p.m.
PD Predicate disambiguation batch_69ad9df25d4c81908ff0f6cff55d0563 completed March 8, 2026, 4:04 p.m.
Created at: March 8, 2026, 3:03 p.m.