Triple
T26176756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IY |
E654563
|
entity |
| Predicate | hasHighByte |
P160017
|
FINISHED |
| Object | IYH |
—
|
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: IYH | Statement: [IY, hasHighByte, IYH]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighByte Context triple: [IY, hasHighByte, IYH]
-
A.
highByte
chosen
Indicates that one value represents the most significant (high-order) byte of another multi-byte value.
-
B.
hasHigh
Indicates that an entity possesses a high level, degree, or intensity of a specified attribute or property.
-
C.
hasHighPropertyValues
Indicates that the associated entity possesses property values that are above a defined or typical threshold.
-
D.
hasByteValues128to255
Indicates that the subject includes or is associated with byte values in the numeric range 128 through 255.
-
E.
hasBit
Indicates that one entity possesses, contains, or includes a specific bit or binary position/value of 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 26, 2026, 8:38 p.m.