Triple

T9933368
Position Surface form Disambiguated ID Type / Status
Subject RIPE Atlas E192697 entity
Predicate hasAPI P182 FINISHED
Object REST API E183290 NE 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: REST API | Statement: [RIPE Atlas, hasAPI, REST API]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: REST API
Context triple: [RIPE Atlas, hasAPI, REST API]
  • A. REST API chosen
    A REST API is a web service interface that allows clients to interact with resources over HTTP using standard methods like GET, POST, PUT, and DELETE in a stateless, structured way.
  • B. API
    The Anton Pannekoek Institute for Astronomy (API) is a research institute at the University of Amsterdam dedicated to astronomical and astrophysical research and education.
  • C. Restout
    Restout is a French surname associated with a notable family of painters active from the 17th to 18th centuries.
  • D. Web APIs
    Web APIs are browser-provided interfaces that enable JavaScript to interact with web platform features such as the DOM, networking, storage, and multimedia beyond the core ECMAScript language.
  • E. JSON API
    JSON API is a standardized specification for building JSON-based RESTful APIs that defines how clients should request and modify resources in a consistent, structured format.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca82dd978c8190947124ab0d3315ac completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cdb5b89c808190a2e766025dd53bd5 completed April 2, 2026, 12:18 a.m.
NED1 Entity disambiguation (via context triple) batch_69d228d1620c8190ac7125b268dd6832 completed April 5, 2026, 9:18 a.m.
Created at: March 30, 2026, 8:44 p.m.