Triple
T29443803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSEC3PARAM |
E746789
|
entity |
| Predicate | flagsFieldType |
P4541
|
FINISHED |
| Object | 8-bit unsigned integer |
—
|
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: 8-bit unsigned integer | Statement: [NSEC3PARAM, flagsFieldType, 8-bit unsigned integer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flagsFieldType Context triple: [NSEC3PARAM, flagsFieldType, 8-bit unsigned integer]
-
A.
fieldType
chosen
Indicates the classification or category that defines the nature or kind of a given field within a structure or context.
-
B.
iterationsFieldType
Indicates that the predicate specifies the data type used for the iterations field in a repeated or iterative process.
-
C.
fieldName
Indicates the specific name or label assigned to a field within a data structure, form, or record.
-
D.
definesField
Indicates that one entity specifies or declares a particular field or attribute that belongs to or characterizes another entity.
-
E.
fieldAdvanced
Indicates that a particular field or attribute has progressed beyond a basic or standard level, reflecting a more complex, specialized, or developed state.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66b1f46cc8190aeed9e77976f5cd1 |
completed | May 2, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 3:25 p.m.