Triple

T3427203
Position Surface form Disambiguated ID Type / Status
Subject Geocoding API E72252 entity
Predicate supportsClientSideUse P15794 FINISHED
Object restricted and discouraged 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: restricted and discouraged | Statement: [Geocoding API, supportsClientSideUse, restricted and discouraged]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsClientSideUse
Context triple: [Geocoding API, supportsClientSideUse, restricted and discouraged]
  • A. supportsUse chosen
    Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
  • B. supportsUnregisteredUse
    Indicates that an entity allows or enables the use of something without requiring prior registration or formal enrollment.
  • C. supportedAs
    Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
  • D. supportsImplementationOf
    Indicates that one entity provides the necessary resources, framework, or assistance for another entity to be carried out, realized, or put into practice.
  • E. usedSupport
    Indicates that one entity employed or relied on another entity as a means of support or assistance in performing an action or achieving a result.
  • 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_69ad85ae14308190bcbc25cfa0246c0b completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb982792c8190b1163eee4252210f completed March 8, 2026, 6:01 p.m.
PD Predicate disambiguation batch_69adadfea024819094b41a13bc004bda completed March 8, 2026, 5:12 p.m.
Created at: March 8, 2026, 3:15 p.m.