Triple

T20610563
Position Surface form Disambiguated ID Type / Status
Subject StreetPass E506435 entity
Predicate regionBehavior P140750 FINISHED
Object works across regions if software is compatible 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: works across regions if software is compatible | Statement: [StreetPass, regionBehavior, works across regions if software is compatible]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regionBehavior
Context triple: [StreetPass, regionBehavior, works across regions if software is compatible]
  • A. regionException
    Indicates an exception or exclusion to a rule, condition, or classification that applies specifically to a certain region or set of regions.
  • B. regionRuled
    Indicates that a particular region is governed or controlled by a specified ruler or authority.
  • C. regionContext
    Indicates the broader geographic or spatial setting within which an entity, event, or relationship is situated or interpreted.
  • D. regionType
    Indicates the classification or category of a region, specifying what kind of region it is (e.g., administrative, geographic, or functional).
  • E. regionImplied
    Indicates that a broader or more general region is inferred or assumed from a given, more specific regional reference.
  • 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_69e0b4bb2b4081908fa4a72444120f35 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6aad6f53481908fb242947dda7028 completed April 20, 2026, 10:38 p.m.
PD Predicate disambiguation batch_69e5a00c43308190b7ea58d559257e07 completed April 20, 2026, 3:39 a.m.
PDg Predicate description generation batch_69e5a6a9f3f88190b961db9aca36f7da completed April 20, 2026, 4:08 a.m.
Created at: April 16, 2026, 11:41 a.m.