Triple
T17568953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Key-Value Observing |
E427885
|
entity |
| Predicate | introducedIn |
P513
|
FINISHED |
| Object | Cocoa |
—
|
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: Cocoa | Statement: [Key-Value Observing, introducedIn, Cocoa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cocoa Context triple: [Key-Value Observing, introducedIn, Cocoa]
-
A.
Cocoa
chosen
Cocoa is Apple’s native object-oriented application framework for building graphical user interfaces and other software on macOS.
-
B.
Cocoa
Cocoa is the dried and processed seed of the cacao tree, widely cultivated in tropical regions for use in chocolate, beverages, and various food products.
-
C.
Cocoa
Cocoa is a small city on Florida’s Space Coast known for its historic downtown, proximity to Cape Canaveral, and role as a local educational hub.
-
D.
Mocha
Mocha is a popular JavaScript test framework used primarily for running unit and integration tests in Node.js and browser-based applications.
-
E.
Mocha
Mocha is a subsidiary peak of the Carihuairazo volcanic massif in the Ecuadorian Andes.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4592f29d08190bc3de905d35af849 |
completed | April 19, 2026, 4:25 a.m. |
Created at: April 10, 2026, 5:50 a.m.