Triple
T33027584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | REST |
E845082
|
entity |
| Predicate | parameterUnit |
P12631
|
FINISHED |
| Object | Bytes from beginning of file |
—
|
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: Bytes from beginning of file | Statement: [REST, parameterUnit, Bytes from beginning of file]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parameterUnit Context triple: [REST, parameterUnit, Bytes from beginning of file]
-
A.
natureOfUnit
Indicates the type or category that characterizes what kind of unit something is (e.g., its nature or classification as a unit).
-
B.
unitOfMeasure
chosen
Indicates that one entity specifies the standard unit in which the quantity or value of another entity is measured.
-
C.
designationUnit
Indicates that one entity serves as the unit or standard of measure used to designate, label, or quantify another entity.
-
D.
inputUnit
Indicates that one entity serves as the unit of measurement or reference in which another entity’s value, quantity, or input is expressed.
-
E.
typeOfUnit
Indicates that one entity specifies the kind or category of measurement unit that the other entity belongs to.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:23 a.m.