Triple
T29389606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | android.print.PrintAttributes.Margins |
E745339
|
entity |
| Predicate | dataTypeOfFields |
P4541
|
FINISHED |
| Object | 32-bit signed 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: 32-bit signed integer | Statement: [android.print.PrintAttributes.Margins, dataTypeOfFields, 32-bit signed integer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataTypeOfFields Context triple: [android.print.PrintAttributes.Margins, dataTypeOfFields, 32-bit signed integer]
-
A.
dataDatatype
Indicates that a piece of data is associated with, or constrained to, a specific datatype.
-
B.
dataTypes
Indicates that one entity specifies or defines the kinds or formats of data that are valid or expected for another entity.
-
C.
dataTypeModel
Indicates that one entity serves as the data type or schema model that defines the structure or format of another entity.
-
D.
fieldType
chosen
Indicates the classification or category that defines the nature or kind of a given field within a structure or context.
-
E.
analyzesDataType
Indicates that one entity examines, interprets, or evaluates a particular type or category of data.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669d578608190962d35116a01420c |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:41 p.m.