Triple
T17817123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Christie |
E444873
|
entity |
| Predicate | associatedWith |
P37
|
FINISHED |
| Object | REST APIs |
—
|
NE NERFINISHED |
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 APIs | Statement: [Tom Christie, associatedWith, REST APIs]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: REST APIs Context triple: [Tom Christie, associatedWith, REST APIs]
-
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.
REST
REST is an FTP command used to specify a restart point for resuming interrupted file transfers.
-
C.
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.
-
D.
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.
-
E.
APIKit
APIKit is a MuleSoft framework for rapidly designing, implementing, and managing RESTful APIs within the Anypoint Platform.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48880457c81908214741d6cd7a1ee |
completed | April 19, 2026, 7:47 a.m. |
Created at: April 10, 2026, 10:14 a.m.