Triple
T26409250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SubBytes |
E663913
|
entity |
| Predicate | appliedIndependentlyTo |
P2335
|
FINISHED |
| Object | each state byte |
—
|
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: each state byte | Statement: [SubBytes, appliedIndependentlyTo, each state byte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedIndependentlyTo Context triple: [SubBytes, appliedIndependentlyTo, each state byte]
-
A.
appliesAcross
chosen
Indicates that a condition, rule, or property holds uniformly over multiple items, cases, or contexts.
-
B.
appliesAlsoTo
Indicates that a condition, rule, or characteristic that applies to one entity is additionally applicable to another entity.
-
C.
appliedFrom
Indicates that an application or request was initiated starting at or originating from a particular source, location, or context.
-
D.
appliesEvenIf
Indicates that a condition, rule, or effect remains valid and in force regardless of whether a specified circumstance or exception occurs.
-
E.
worksIndependentlyOf
Indicates that one entity performs its function or activity without relying on, being influenced by, or requiring coordination with another entity.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 26, 2026, 11:37 p.m.