Triple
T6991555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UTF-8 |
E162096
|
entity |
| Predicate | leadingBytePattern |
P74325
|
FINISHED |
| Object | 0xxxxxxx for 1-byte sequences |
—
|
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: 0xxxxxxx for 1-byte sequences | Statement: [UTF-8, leadingBytePattern, 0xxxxxxx for 1-byte sequences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadingBytePattern Context triple: [UTF-8, leadingBytePattern, 0xxxxxxx for 1-byte sequences]
-
A.
branchingPattern
Indicates the structural way in which one element divides into multiple offshoots or subdivisions from a common source.
-
B.
notationPattern
Indicates a recurring way in which something is symbolically represented or written, such as a consistent style or structure of notation used for an entity or concept.
-
C.
recognizedFirstBy
Indicates that one entity was the earliest or initial recognizer, identifier, or acknowledger of another entity.
-
D.
precedesLetter
Indicates that one letter comes immediately before another letter in a specified ordering, such as the alphabet or a given sequence.
-
E.
capturesCharacter
Indicates that one entity seizes, traps, or takes control of another character.
- 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_69c68856d7808190ab33ee914640281b |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbc1f63c8190837cfd71cf5ed613 |
completed | March 27, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6dbbc00fc8190a18221524b774021 |
completed | March 27, 2026, 7:34 p.m. |
Created at: March 27, 2026, 2:32 p.m.