Triple
T20337214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10GBASE-W WAN PHY |
E495644
|
entity |
| Predicate | usesLayering |
P36580
|
FINISHED |
| Object | reconciliation sublayer |
—
|
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: reconciliation sublayer | Statement: [10GBASE-W WAN PHY, usesLayering, reconciliation sublayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLayering Context triple: [10GBASE-W WAN PHY, usesLayering, reconciliation sublayer]
-
A.
supportsLayerHierarchy
Indicates that one element can contain and organize other elements within a structured, ordered layer system.
-
B.
isTypicallyLayered
Indicates that something is usually composed of multiple distinct layers arranged one on top of another.
-
C.
layerOf
chosen
Indicates that one entity forms a distinct layer or stratum of another entity within a structured or composite whole.
-
D.
layerType
Indicates the specific kind or category of layer that an entity belongs to or is classified as.
-
E.
supportsLayeredDivisionMultiplexing
Indicates that one entity enables or is compatible with the use of layered division multiplexing techniques in conjunction with 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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677ed75e081909bfc534033ac1c59 |
completed | April 20, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:23 a.m.