Triple

T1880073
Position Surface form Disambiguated ID Type / Status
Subject Baduy E39831 entity
Predicate transportationRule P29930 FINISHED
Object prohibition on motorized vehicles in core territory 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: prohibition on motorized vehicles in core territory | Statement: [Baduy, transportationRule, prohibition on motorized vehicles in core territory]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: transportationRule
Context triple: [Baduy, transportationRule, prohibition on motorized vehicles in core territory]
  • A. roadTrafficRuleJurisdiction
    Indicates the jurisdiction or authority under whose road traffic rules a given situation, entity, or action is governed.
  • B. transports
    Indicates that one entity carries or conveys another entity from one place to another.
  • C. trafficRestriction chosen
    Indicates a limitation or prohibition on the movement or flow of traffic between entities, such as vehicles, routes, or areas.
  • D. transportRole
    Indicates that an entity participates in a transportation process with a specific functional role (e.g., carrier, passenger, cargo, or operator).
  • E. fareControl
    Indicates that an entity is responsible for monitoring, enforcing, or managing payment of fares for access to a service or facility.
  • 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_69a88633e4fc8190b7eb40463e048ec5 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb4f53f408190ae30e1a12721e7d7 completed March 7, 2026, 5:17 a.m.
PD Predicate disambiguation batch_69abafe497a88190a1da6af2888b71b4 completed March 7, 2026, 4:56 a.m.
Created at: March 4, 2026, 7:34 p.m.