Triple
T10046391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mac OS X 10.4 Tiger |
E207625
|
entity |
| Predicate | includedAPI |
P1393
|
FINISHED |
| Object | Core Data API |
E284600
|
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: Core Data API | Statement: [Mac OS X 10.4 Tiger, includedAPI, Core Data API]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Core Data API Context triple: [Mac OS X 10.4 Tiger, includedAPI, Core Data API]
-
A.
Core Data
chosen
Core Data is Apple’s object graph and persistence framework used in macOS and iOS apps to manage and store model layer data.
-
B.
DataSet API
DataSet API is Apache Flink’s now-legacy batch processing API for defining and executing scalable, distributed data transformations.
-
C.
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.
-
D.
OData
OData (Open Data Protocol) is a standardized, REST-based protocol for querying and updating data over the web, commonly used to expose and consume interoperable APIs.
-
E.
REST API
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.
- 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_69ca835ad0608190b7c80b292da004f5 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcf648f548190a7aa3b1594665831 |
completed | April 2, 2026, 2:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d282888bac81909ccb5db5724c416d |
completed | April 5, 2026, 3:40 p.m. |
Created at: March 30, 2026, 8:56 p.m.