Triple
T20271137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10GBASE-E |
E499094
|
entity |
| Predicate | usesLANPHY |
P10595
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [10GBASE-E, usesLANPHY, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLANPHY Context triple: [10GBASE-E, usesLANPHY, yes]
-
A.
usedByNetwork
Indicates that something is utilized or operated by a particular network.
-
B.
usesPhysicalLayerSimilarTo
chosen
Indicates that one entity employs a physical layer that is similar in structure, technology, or operational characteristics to that used by another entity.
-
C.
usesBasebandTransmission
Indicates that one entity employs baseband transmission, meaning it sends digital signals directly over a communication medium without modulating them onto a higher-frequency carrier.
-
D.
usesPhysicalLanes
Indicates that an entity operates or organizes movement through distinct, physically separated lanes or pathways.
-
E.
usesIP
Indicates that one entity makes use of, operates through, or is associated with a particular IP address.
- 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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e675de35188190840dc7d04c1d5fd9 |
completed | April 20, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:42 p.m.