Triple
T17417285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Context-Adaptive Binary Arithmetic Coding |
E423519
|
entity |
| Predicate | codingDomain |
P127369
|
FINISHED |
| Object | binary symbols |
—
|
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: binary symbols | Statement: [Context-Adaptive Binary Arithmetic Coding, codingDomain, binary symbols]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codingDomain Context triple: [Context-Adaptive Binary Arithmetic Coding, codingDomain, binary symbols]
-
A.
code
Indicates that an entity writes, develops, or produces computer software or source code.
-
B.
softwareDomain
Indicates that something belongs to, operates within, or is associated with a particular area or field of software.
-
C.
creativeDomain
Indicates the domain or field of creative activity within which an entity produces or expresses its work.
-
D.
programmingLanguage
Indicates that one entity is a programming language used to create, control, or interact with the other entity.
-
E.
programming
Indicates that an entity writes, develops, or modifies software or code, typically using a programming language to create or control computer programs.
- F. None of above. chosen
Provenance (4 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44233c7888190a4d2aa703b206851 |
completed | April 19, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:46 a.m.