Triple
T18564694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Base64 |
E453732
|
entity |
| Predicate | bitGrouping |
P28527
|
FINISHED |
| Object | splits 24 bits into 4 groups of 6 bits |
—
|
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: splits 24 bits into 4 groups of 6 bits | Statement: [Base64, bitGrouping, splits 24 bits into 4 groups of 6 bits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bitGrouping Context triple: [Base64, bitGrouping, splits 24 bits into 4 groups of 6 bits]
-
A.
bitOrder
Indicates the ordering or sequence of bits within a binary representation, such as which bit positions are considered first or most significant.
-
B.
bitSlice
chosen
Indicates taking a contiguous subset of bits from a larger bit sequence, defined by specified start and end positions.
-
C.
buttonGrouping
Indicates that multiple buttons are associated together as a single logical or functional group.
-
D.
ISOGroupingStatus
Indicates the relationship between an entity and its classification or status within an ISO-defined grouping or category.
-
E.
groupingType
Indicates how multiple entities are categorized or clustered together based on a shared grouping criterion.
- F. None of above.
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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53afd8114819093b57d86f8213311 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:42 a.m.