Triple
T37164255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DVB-SH |
E920751
|
entity |
| Predicate | usesLayer |
P187493
|
FINISHED |
| Object | physical layer |
—
|
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: physical layer | Statement: [DVB-SH, usesLayer, physical layer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLayer Context triple: [DVB-SH, usesLayer, physical layer]
-
A.
layerOf
Indicates that one entity forms a distinct layer or stratum of another entity within a structured or composite whole.
-
B.
usesSurface
Indicates that one entity employs or interacts with another entity as a surface or platform for its action or function.
-
C.
targetsLayer
Indicates that one entity is directed at, operates on, or is specifically intended to affect a particular layer within a layered structure or system.
-
D.
isLayeredOver
Indicates that one entity is positioned or arranged directly on top of another, partially or fully covering it in a layered manner.
-
E.
featureLayer
Indicates that one entity functions as a feature layer associated with, or used within, another entity (such as a map, dataset, or visualization context).
- F. None of above. chosen
Provenance (4 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb55dc36d08190a0634fa680e13114 |
completed | May 6, 2026, 2:53 p.m. |
Created at: May 3, 2026, 4:15 p.m.