Triple
T10168103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OER |
E235256
|
entity |
| Predicate | encodingUnit |
P70325
|
FINISHED |
| Object | octet |
—
|
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: octet | Statement: [OER, encodingUnit, octet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encodingUnit Context triple: [OER, encodingUnit, octet]
-
A.
codingUnit
Indicates a relationship where an entity functions as or is associated with a specific unit of code or coding structure.
-
B.
representationUnit
chosen
Indicates a relationship where one entity serves as the representational unit or basic representational component used to express, encode, or stand in for another entity or concept.
-
C.
definesUnit
Indicates that one entity specifies the measurement unit or standard by which the value or quantity of another entity is expressed.
-
D.
unitOfMeasure
Indicates that one entity specifies the standard unit in which the quantity or value of another entity is measured.
-
E.
basedUnit
Indicates that one unit is defined in terms of, or derived from, another more fundamental unit.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec6f64a48190883aefce58a65ca6 |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba9956c8190a3e15d091e33149d |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:10 p.m.