Triple
T28619742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resource Interchange File Format |
E724350
|
entity |
| Predicate | sizeFieldSize |
P7759
|
FINISHED |
| Object | 32-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: 32-bit unsigned integer | Statement: [Resource Interchange File Format, sizeFieldSize, 32-bit unsigned integer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sizeFieldSize Context triple: [Resource Interchange File Format, sizeFieldSize, 32-bit unsigned integer]
-
A.
fieldSize
chosen
Indicates the magnitude or dimensions of a field associated with an entity or context.
-
B.
sizeType
Indicates the kind or category of size associated with an entity, such as relative scale, measurement type, or size classification.
-
C.
sizeDefinedBy
Indicates that the size or magnitude of one entity is determined, constrained, or specified by another entity.
-
D.
setSize
Indicates assigning or changing the size or dimensions of an entity.
-
E.
sizeDescription
Indicates a relationship where one entity provides descriptive information about the size or scale 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:32 a.m.